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. — Boris Beizer Copy Share Image
If you can't test it, don't build it. If you don't test it, rip it out. — Boris Beizer Copy Share Image
Testing proves a programmer’s failure. Debugging is the programmer’s vindication. — Boris Beizer Copy Share Image
More than the act of testing, the act of designing tests is one of the best bug preventers known. — Boris Beizer Copy Share Image
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… — Boris Beizer Copy Share Image
If the objective of testing were to prove that a program is free of bugs, then not only would testing be practically impossible, but… — Boris Beizer Copy Share Image
Second law: The complexity barrier. Software complexity (and therefore that of bugs) grows to the limits of our ability to manage that complexity. — Boris Beizer Copy Share Image
First law: The pesticide paradox. Every method you use to prevent or find bugs leaves a residue of subtler bugs against which those methods… — Boris Beizer Copy Share Image
A design remedy that prevents bugs is always preferable to a test method that discovers them. — Boris Beizer Copy Share Image
In programming, it’s often the buts in the specification that kill you. — Boris Beizer Copy Share Image
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… — Boris Beizer Copy Share Image
