42. The animistic metaphor of the bug
that maliciously sneaked in while the
programmer was not looking...
disguises that the error is the
programmer's own creation.
— Edsger Dijkstra
43. The whole time I’m programming, I’m
constantly checking my assumptions.
—Rasmus Lerdorf
@loriabys
44. As you're about to add a comment, ask
yourself, “How can I improve the code
so that this comment isn't needed?”
Improve the code and then document
it to make it even clearer.
— Steve McConnell
45. 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.
—Brian Kernighan
48. An organization's defenses against failure
are a series of barriers, represented as
slices of swiss cheese. The holes in the
cheese represent weaknesses in
individual parts of the system. Failures
occur when a hazard passes through all
of the holes in all of the defenses.
— Wikipedia
94. Customer Experience is as much about technology as it
is about product requirements
NASA
95. Most bugs, most of the time, are easily
nailed given even an incomplete but
suggestive characterization of their
error conditions at source-code level.
— Eric S. Raymond
124. Further Reading
“How Google Tests Software,” James Whittaker
“Look At Your Data,” John Rausser
“Optimizing For Developer Happiness,” Chad Dickerson
“Outages, Postmortems and Human Error,” John Allspaw
http://en.wikipedia.org/wiki/Swiss_cheese_model
“What Is Exploratory Testing?,” James Bach