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
Chopped and disfigured The details of a building cannot be made alive when they are made from modular parts If the builder wants to build the room from modular four-foot panels, he must change the size of the rooms, and change their shape, to fit his panels. In such a building system, it is impossible for a person to create a plan which reflects the larger subtleties of site or plan. Each plan will always be chopped and disfigured to make it fit the building details. To make the building live, its patterns must be generated on the site, so that each one takes its own shape according to its context. Christopher Alexander, The Timeless Way of Building What's suitable for each unique condition modularity