I have a strong appreciation for the ideas behind the Software Craftmanship Movement, but find myself to be simultaneously overwhelmed and a bit annoyed by the seemingly unending rhetoric that comes along with it. Since I'm probably not alone here, I've tried to collect a very short list of guidelines for those looking to practice small-c craftsmanship as a software developer. They are, in no particular order:
- Remember that anything worth doing is worth doing well.
- Care about your work and work on the things that you care about.
- Learn from skilled mentors, but don't forget to pay it forward.
- Treat techniques and methodologies as tools, not religions
- Above all, don't forget to ship real works often!
Personally, I don't feel we need to evangelize these basic points. Instead, we should collaborate with others who share these common values, and then collectively demonstrate their worth through the fruits of our labor. This is what I am doing with Ruby Mendicant University, and I hope it's what you'll do in your own organizations as well. The true software craftsmanship revoution will not be televised.