Today's postings about writing bug-free code, creating
flow charts, and all the rest of it miss the point I was
trying to make.
There's probably very little significant code written that
is bug-free the first time it's run. So that wasn't my
issue.
But the software has to be tested. My point was that
if TT spent 10 or 15 minutes testing these new features
when they add them, they could fix the problems
before the updates are released.
Doing right the first time probably doesn't take any
more time that having to do it over a second time.
And they look better to their customers when it's
right the first time.
Which brings up another point. To do a truly comprehensive
test, they not only need to test the new features, but they
need to go back and test EVERYTHING ELSE, to make
sure they didn't break something that used to work.
Does anybody remember last August or September,
when they released four Jupiter updates in four or five
days?
The new firmware version broke something, so they
fixed that, but broke something else. Then they fixed
that, but broke something else.
Finally, after four attempts, they got it back the way it
was before they changed it.
I bet if they would have done some testing before they
sent the updates out they would have saved all of us
the trouble of having to install four updates when one
should have been sufficient.
So my point is simply that they need to spend more time
checking their work before they send it out into the world.
I'm truly baffled that some folks are willing to accept
having to install the software two or three times before
it's correct.
73,
Mike - WB4HUC
Austin, TX
|