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
Merely a building Eisenman: Le Corbusier once defined architecture as having to do with a window which is either too large or too small, but never the right size. Once it was the right size it was no longer functioning. When it is the right size, that building is merely a building. The only way in the presence of architecture that is that feeling, that need for something other, when the window was either too large or too small. Christopher Alexander & Peter Eisenman, Contrasting Concepts of Harmony in Architecture A little too something flaws