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
Invisible substance We wanted wood, not only in many visible places, but also in the roof trusses of the homeroom buildings, where they are invisible. Fujita wanted to replace the invisible trusses with steel trusses. They could not understand the idea that it was the actual substance — even though not visible — which would control the feeling of the thing. Christopher Alexander, The Battle for the Life and Beauty of the Earth All the way throughFinished on the inside material