Hans Reiser in Interview
The things that don’t make sense are the most important data collected. Time and again, getting to the bottom of a minor performance anomaly that should not exist reveals a design flaw or failure in my understanding, and curing it leads to an advance in our performance that was well worth having. Time and again I have learned the importance of not letting any code go in without benchmarking it. Things that could not possibly affect performance, do, over and over again, and if you don’t catch it immediately, you might never catch it.
Hans Reiser in interview shares some of the most important lessons he’s learned in his career as a software developer/architect.