-
By AnonymBoris Beizer
A design remedy that prevents bugs is always preferable to a test method that discovers them.
00 -
By AnonymBoris Beizer
A good threat is worth a thousand tests.
00 -
By AnonymBoris Beizer
Bugs lurk in corners and congregate at boundaries.
00 -
By AnonymBoris Beizer
First law: The pesticide paradox. Every method you use to prevent or find bugs leaves a residue of subtler bugs against which those methods are ineffective.
00 -
By AnonymBoris Beizer
If the objective of testing were to prove that a program is free of bugs, then not only would testing be practically impossible, but it would also be theoretically impossible.
00 -
By AnonymBoris Beizer
If you can't test it, don't build it. If you don't test it, rip it out.
00 -
By AnonymBoris Beizer
In programming, it’s often the buts in the specification that kill you.
00 -
By AnonymBoris Beizer
More than the act of testing, the act of designing tests is one of the best bug preventers known.
00 -
By AnonymBoris Beizer
One of the saddest sights to me has always been a human at a keyboard doing something by hand that could be automated. It's sad but hilarious.
00 -
By AnonymBoris Beizer
Second law: The complexity barrier. Software complexity (and therefore that of bugs) grows to the limits of our ability to manage that complexity.
00 -
By AnonymBoris Beizer
Software never was perfect and won't get perfect. But is that a license to create garbage? The missing ingredient is our reluctance to quantify quality.
00 -
By AnonymBoris Beizer
Anything written by people has bugs. Not testing something is equivalent to asserting that it's bug-free. Programmers can't think of everything especially of all the possible interactions between features and between different pieces of software. We try to break software because that's the only practical way we know of to be confident about the product's fitness for use.
00