Programming Quotes
-
Would you hire someone who didn't bother to proofread their e-mails, but claimed to advocate quality improvement through testing? What would you hire that person to do?
-
Isn't it better to think of testing as an integral part of the development process, and not separate from it? I think too many "developers" treat testing as a separate process to development when in fact testing *is* part of development! I prefer to code to a specification and then use testing to confirm the result. If a test fails then I cycle back to the code and repeat until all tests pass.... ...then I wait for the customer's user acceptance testing to tell me what I missed! :doh:
-
OK, heres the spec: 1) It has to work. So how do you fold that into a classic spec-design-test scenario. You cant.
Truth is the subjection of reality to an individuals perception
Ah yes, “make it work.” Many years ago I attended a programming enrichment class sponsored by my employer. The guy that gave the class was a “it all about the specs” kind of guy. I joked and suggested that if the spec was that rigorous that one could develop a spec compiler and dispense with software jobs completely. He said that a spec compiler existed and offered to take my card and send me something about it. I never got it. Even when I had an interface spec I managed to get opcodes changed to a series of bits – one bit for each action I was to perform. Thus I had one bit for write another for read, another for multi-record format and another one or two that I forget. It saved the day because due to the excessive compute overhead of VM360 with I/O we had to add a multi-track bit. And the thing worked for every opcode bit pattern. Precognition or luck? It sure wasn’t the spec. Somebody hire me. Check out http://hmtown.com
-
Ah yes, “make it work.” Many years ago I attended a programming enrichment class sponsored by my employer. The guy that gave the class was a “it all about the specs” kind of guy. I joked and suggested that if the spec was that rigorous that one could develop a spec compiler and dispense with software jobs completely. He said that a spec compiler existed and offered to take my card and send me something about it. I never got it. Even when I had an interface spec I managed to get opcodes changed to a series of bits – one bit for each action I was to perform. Thus I had one bit for write another for read, another for multi-record format and another one or two that I forget. It saved the day because due to the excessive compute overhead of VM360 with I/O we had to add a multi-track bit. And the thing worked for every opcode bit pattern. Precognition or luck? It sure wasn’t the spec. Somebody hire me. Check out http://hmtown.com
Yep, I do device drivers. They have one spec. It has to work. For ever, without BSODing the PC. That means not one single exception, not one single fault, ever. The code has to be perfect. And you only get that by testing it to destruction, untill every line of code has been run in every situation the user is ever going to find himself in. And the fools on this forum tell me testing doesnt make a better product!
Truth is the subjection of reality to an individuals perception