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
Their wrongness is somehow more immediate In general, a successful design, which Alexander terms a good fit between form and context, can be declared only when we can detect no more [points that conform to the standard against which we judge]. It is "departures from the norm which stand out in our minds, rather than the norm itself. Their wrongness is somehow more immediate than the rightness." Henry Petroski, The Evolution of Useful Things Notes on the Synthesis of Form