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
Scraps of the brocade of autumn There is a story of Rikyu which well illustrates the ideas of cleanliness entertained by the tea masters. Rikyu was watching his son Shoan as he swept and watered the garden path. "Not clean enough," said Rikyu, when Shoan had finished his task, and bade him try again. After a weary hour the son turned to Rikyu: "Father, there is nothing more to be done. The steps have been washed for the third time, the stone lanterns and the trees are well sprinkled with water, moss and lichens are shining with a fresh verdure; not a twig, not a leaf have I left on the ground" "Young fool," chided the tea master, "that is not the way a garden path should be swept. "Saying this, Rikyu stepped into the garden, shook a tree and scattered over the garden gold and crimson leaves, scraps of the brocade of autumn! What Rikvu demanded was not cleanliness alone, but the beautiful and the natural also. Okakura Kakuzō, The Book of Tea In a state of reverberation wabi-sabi