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
Deliberate acts I do not know what one should call the landscape of a long cultivated countryside, or the enchanting pattern of lights which shows at night time in a modern city seen from overhead. Are these not works of art? It is scarcely justifiable to say that these things have taken shape by chance. Each part of them has been made as it is by what seemed a deliberate act, and it need not necessarily be assumed to be a matter of chance that the results of many acts of many men over a considerably period of time should harmonize together aesthetically. David Pye, The Nature and Aesthetics of Design The Timeless Way of BuildingA Pattern Language evolutionurbanism