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 details of construction The housing developments in the Moscow suburbs were built mostly in the decades after the Second World War. Laid out as enormous chessboards, the suburbs stretch to the horizon across flat land sparsely planted with birch and aspen. The architectural design of the suburban buildings was good, but the state had not been able to command good-quality work. The signs of poorly motivated workers appeared in the details of construction. Richard Sennett, The Craftsman Designing detail