“Baseball men, living from day to day in the clutch of carefully metered chance occurrences, have developed an entire bestiary of imagined causes to tie together and thus make sense of patterns that are in truth entirely accidental,” James wrote. “They have an entire vocabulary of completely imaginary concepts used to tie together chance groupings. It includes ‘momentum,’ ‘confidence,’ ‘seeing the ball well,’ ‘slumps,’ ‘guts,’ ‘clutch ability,’ being ‘hot’ and ‘cold,’ ‘not being aggressive’ and my all time favorite the ‘intangibles.’ By such concepts, the baseball man gains a feeling of control over a universe that swings him up and down and tosses him from side to side like a yoyo in a high wind.” It wasn’t just baseball he was writing about, James continued. “I think that the randomness of fate applies to all of us as much as baseball men, though it might be exacerbated by the orderliness of their successes and failures.”

"Failure does not strike like a bolt from the blue; it develops gradually according to its own logic." -- Dietrich Dorner

Little things can make a big difference, but only after the big things have been taken care of.
    -- Ward Cunningham

Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don’t improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don’t buy a new scale; change your diet. If you want to improve your software, don’t test more; develop better.
    -- Steve C. McConnell, Code Complete: A Practical Handbook of Software Construction, 1993

(Thanks to Jean McAuliffe)