Ever wonder how to measure and tune your application's performance? In Performance Tuning Apache and Passenger, I show how we used httperf, htop, iftop, and a handful of other tools to measure, tune, and identify performance hotspots in your application. While this deals a lot with Rails, Apache, and Passenger, what I cover about the use of the tools apply to any http server-side process.
Ever deploy a rails application that seemed slow once it had real data in it? Ever tweak a few things in your my.cnf and it perked things up, but really didn't know what the correct values should be? My blog entry on 4 Mysql settings you should tune and how to tune them might be just the performance prescription you need.
A colleague of mine recently wrote rescue_me, a small wrapper for exception-generating code that retries with exponential backoff. We had to connect to a sporadically flaky webservice, and this bit of code made our stuff a lot more robust with minimal effort.
I have been thinking about an agile maturity assessment model for years, as this blog article illustrates. Its time to take it to the next level with this blog series. I'm inviting mature discussion, realizing that there will be a small controversy about this. I'm hoping it acts as a forge for the ideas.