The rules of Optimization Club

From David Fetter's page at

  1. The first rule of Optimization Club is, you do not Optimize.
  2. The second rule of Optimization Club is, you do not Optimize without measuring.
  3. If your app is running faster than the underlying transport protocol, the optimization is over.
  4. One factor at a time.
  5. No marketroids, no marketroid schedules.
  6. Testing will go on as long as it has to.
  7. If this is your first night at Optimization Club, you have to write a test case.

Of course it's company policy never to imply ownership of a performance problem. Always use the indefinite article: "a performance problem", never "your performance problem."



Max said:

That is hilarious. :-) Number 3 in particular made me laugh out loud, it definitely struck a chord. :-)


Leave a comment

About this Entry

This page contains a single entry by Andy Lester published on February 19, 2008 5:54 PM.

Leopard cheat sheet was the previous entry in this blog.

Free up a few gigabytes of space on your Mac is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Other Perl Sites

Other Swell Blogs

  • geek2geek: An ongoing analysis of how geeks communicate, how we fail and how to fix it.