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
To see the fulfillment of the work It is true that [the artist], like everybody else, derives remuneration from his work (though not, strictly speaking, profit in the financial sense, of the word, since what he invests in his work is not money but time and skill, whose returns cannot be calculated in percentages). The remuneration is frequently beyond the amount necessary to enable him to go on working. What is remarkable about him is the way in which he commonly employs the escape-from-work which the extra remuneration allows him. If he is genuinely an artist, you will find him using his escape-from-work in order to do what he calls “my own work”, and nine times out of ten, this means the same work (i.e. the exercise of his art) that he does for money. The peculiar charm of his escape is that he is relieved, not from the work but from the money. What distinguishes him here from the man who works to live is, I think, his desire to see the fulfilment of the work. Dorothy Sayers, The Mind of the Maker For its own sakeThe saddest designer craft