The tutorial day for RailsConf 2009 has drawn to a close. I spent the morning in Running the Show: Configuration Management with Chef by Edd Dumbill. The first half of the tutorial was a bit awkward when the live demo failed to get off the ground. While I don’t feel I walked away with any concrete training, I did come away with enough appreciation of Chef that I’m looking forward to learning and using it to rein in the increasing number of nearly identical systems I find myself managing.
In the afternoon I attended Joe O’Brien’s and Jim Weirich’s Testing, Design and Refactoring. The first half of the tutorial consisted of presentation by both Jim and Joe. Part of Jim’s talk included the material from his “Writing Modular Code” talk from Scotland on Rails. Joe’s portion covered some of the general methods of refactoring and why you might use them. One concept that struck a chord with me was the concept (or goal) of simplicity. Simple code has the following characteristics:
- Passes tests, i.e., the code works
- No duplication
- Clearly expresses intent
- Minimal number of classes and methods
And those characteristics are in order of importance. If the code doesn’t work, it doesn’t matter whether or not it’s clear. (I’m a little fuzzy about the order of duplication and clarity in that list though. If eliminating duplication results in loss of clarity, that may not be a net win.)