Tag archive for “Quality and Testing”
“Test-driven development is a way of managing fear during programming.”
“Even so the program works. Is this not just an aesthetic judgment, a dislike of ugly code? It is until we want to change the system. The compiler doesn’t care whether the code is ugly or clean. But when we change the system, there is a human involved, and humans do care. A poorly designed system is hard to change. Hard because it is hard to figure out where the changes are needed. If it is hard to figure out what to change, there is a strong chance that the programmer will make a mistake and introduce bugs.”
“There is No CODE That is More Flexible Than NO Code!”
“As a rule, software systems do not work well until they have been used, and have failed repeatedly, in real applications.”
“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.”
“Don’t keep “trying” solutions until you find one that works. Take the time to find the correct solution.”
“Bugs lurk in corners and congregate at boundaries.”
“Program testing can be used to show the presence of bugs, but never to show their absence!”
“There is an old saying with software that three years from now, no one will remember if you shipped an awesome software release a few months late. What customers will still remember three years from now is if you shipped a software release that wasn’t ready a few months too soon. It takes multiple product releases to change people’s quality perception about one bad release.”