Software Engineering as a Craft An Article by Thomas Wilson thomaswilson.xyz The decreasingly tangible product of code, i.e. that all we have are files on a hard-drive, may make it easy to forget that writing software produces a thing. If you produce a wonky chair or an overly long fork, it’s easy to see the quality of work was not great. By calling for a perception of software as a craft, we fight against that ability to forget or not notice the final quality of the product. You could watch two software engineers with different levels of experience, or in different domains, and it wouldn’t necessarily be so easy to guess which is which, at least from a distance. So maybe there is something to be said for the value of software as a craft, for sometimes focusing on the practice of making better, or at least different, software just for the sake of it. craftsoftware
The reflective craftsman Specialized tools like bench shears have proliferated throughout history in part because craftsmen necessarily do the same task with the same tool over and over. After a while, the task becomes routine, and the craftsman is able to perform it with predictable skill. The most creative of artisans is frequently one who, in the midst of routine, pays attention to the details of the work and the tools that effect that work, and so it is that the reflective craftsman develops ideas for new and improved tools in the course of working with those that he perceives to limit his achievement or efficiency. Henry Petroski, The Evolution of Useful Things Eating your own dog food toolsroutineskill