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 informing idea of functionalism The informing idea of functionalism is what is called elegance by engineers and scientists—the notion that the best solution to a problem (whether applied to a mathematical proof, a machine, or an organizational diagram) is the most succinct. This conceit collapses the technical, the ethical, and the aesthetic, which powers the idea exponentially. Michael Sorkin, 20 Minutes in Manhattan The Nature and Aesthetics of Design functionaesthetics