« A Twitter change of a conference | Main | Sexier software in Australia »
Manifesto for Software Craftsmanship
By Therese Hansen | March 25, 2009
The nature of programming and developing software has been debated a lot recently. At QCon London 2009 Sir Tony Hoare talked in the opening keynote about the communication between the professional developer and the academic computer scientist and how the work should be divided between the two.
In december 2008 the Manifesto for Software Craftsmanship was drafted and since there has been a call for arms to sign this manifesto saying;
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 software.
Not only responding to change, but also steadily adding value.
Not only individuals and interactions, but also a community of professionals.
Not 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.
At JAOO 2007 there was a great trend towards discussing what it ment to be a professional developer and about calling it craftsmanship – this discussion was lead by Robert C. Martin (Uncle Bob wrote “Clean Code: A Handbook of Agile Software Craftsmanship”) and Pete McBreen (Pete wrote “Software Craftsmanship: The New Imperative”).
The CTO of Trifork, Kresten Krab Thorup, did an interview with Robert C. Martin, Pete McBreen and Michael Feathers about this notion of Craftsmanship and we shot this video of it:
