A couple of days ago we talked about the Software Craftsmanship movement at work. I thought of the movement as an extension to the agile movement, that goes full circle to agile’s roots in software development, and focuses on practising coding skills.
This is the Software Craftsmanship Manifesto:
As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value:Not only working software,but also well-crafted softwareNot only responding to change,but also steadily adding valueNot only individuals and interactions,but also a community of professionalsNot only customer collaboration,but also productive partnerships
That is, in pursuit of the items on the left we have found the items on the right to be indispensable.
Some colleagues were irritated that it’s called “craftsmanship”, after all they spent years at university becoming software engineers. But today (the first day of ALE 2011) it made perfect sense, when Markus Gärtner explained the second important aspect of Software Craftsmanship: How new developers are taught and mentored – The ideas include apprenticeship and traveling the world afterwards, the same way journeymen to do, learning from different masters of the craft in each location. There’s even a map showing where software journeymen and -women are welcome.
Thanks, Markus, for a very interesting talk!
Great you found all of the pointers on the web. Indeed the discrepancy between how Software Craftsmanship is perceived, and what it intended to do from the start puzzles me for some time now. We are going local with some communities in Germany, and I hope to explore these ideas even more in that context.
Thanks for the write-up.
Comments are closed.