Recap This is part 2 of a series about finding a structured, repeatable way to optimize software. In part 1 of this series, we talked about a process for making decisions about performance without having to worry about committing the "premature optimization" sin. Basically, it comes down to these steps: 1. Goals - Set some performance goals early in the life of the project and continue to revisit and adjust them as needed. 2. Testing - Test your system to see if it meets the

Optimization has become a tricky subject in the world of software development. The term "premature optimization" is thrown around a lot. Sometimes you hear stories about developers who spend all their time worrying about performance problems they don't actually have. Other times you hear about sluggish, resource hungry systems that have to be heavily reworked or completely scrapped because performance wasn't considered at all. So how does one keep their projects from such fat