| ??? 09/15/05 14:39 Read: times |
#101132 - a disastrous approach Responding to: ???'s previous message |
I reckon measuring the speed of a working system is the best way of determining whether you have a problem.
a disastrous approach. Some day, maybe months out in the future a certain confluence of events happen and BOOM!! it is not "fast enough". You can NOT "measure" the speed!, waaay too many factors make that a variable. Of course, if you have several months for "testing" and are one of the best testers in the world, you might achieve a certain comfort level. I think you should always make it work right, and then make it work fast if neccessary. How are you going to "make it work right" if it is not fast enough. The value of testing" is zero, nada, none except for static errors. How come so many totally ignore that fact that a piece of code operates in a dynamic fashion. I can not recall ANY case where I have been asked to "take a look at" a released product with a lingering bug where the statement "it tested OK" has not been made. Erik |
| Topic | Author | Date |
| compiling in SDCC on 89c52 | 01/01/70 00:00 | |
| Move some variables | 01/01/70 00:00 | |
| all in xdata | 01/01/70 00:00 | |
| go have a cup of coffee | 01/01/70 00:00 | |
| If that isn't enough.. | 01/01/70 00:00 | |
| a disastrous approach | 01/01/70 00:00 | |
| Indeed | 01/01/70 00:00 | |
| we agree, I hope, on both points | 01/01/70 00:00 | |
| Pardon me for breathing | 01/01/70 00:00 | |
| why the need for a pardon | 01/01/70 00:00 | |
| Really? | 01/01/70 00:00 | |
| With Craig on this one | 01/01/70 00:00 | |
the full story | 01/01/70 00:00 | |
| how much | 01/01/70 00:00 |