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
Employs nothing at all The man of today planes to perfection a board with a planing machine in a few seconds. The man of yesterday planed a board reasonably well with a plane. Very primitive man squared a board very badly with a flint or a knife. Very primitive man employed a unit of measurement and regulating lines in order to make his task easier. The Greek, the Egyptian, Michaelangelo or Blondel employed regulating lines in order to correct their work and for the satisfaction of their artist’s sense and of their mathematical thought. The man of today employs nothing at all and the result is the boulevard Raspail. Le Corbusier, Towards a New Architecture The Nature and Art of Workmanship tools