David Bolton Strikes Again

I have no idea of the original source, but this came up in Ruby on Rails Oceania IRC yesterday:

Brilliant!

Good advice on performance testing from a Googler, in particular:

I have seen more bad code developed as a result of premature performance optimizations – before the team even thought they had a problem! Please don’t do that. Develop your service in a clean, maintainable and extensible manner. Let me test it, and keep regression testing it. If we find we have a problem in a particular area, we can then address that problem easily – because our code is not obfuscated with performance optimization that have improved code paths that execute once a month by 5%.

I learnt a lot about Performance Testing at Telstra eBusiness, those were very enlightening times.