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
Five barns worth burning I walked around with a map, penciling in X’s wherever there was a barn or shed. For the next three days, I covered four kilometers in all four directions. Living toward the outskirts of town, there are still a good many farmers in the vicinity. So it came to a considerable number of barns—sixteen altogether. I carefully checked the condition of each of these, and from the sixteen I eliminated all those where there were houses in the immediate proximity or greenhouses alongside. I also eliminated those in which there were farm implements or chemicals or signs that they were still in active use. I didn’t imagine he’d want to burn tools or fertilizer. That left five barns. Five barns worth burning. Haruki Murakami, Barn Burning barnsworthburning.net i