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
Focal awareness The philosopher Maurice Merleau-Ponty describes what she experienced as "being as a thing." The philosopher Michael Polanyi calls it "focal awareness" and recurs to the act of hammering a nail: When we bring down the hammer we do not feel that its handle has struck our palm but that its head has struck the nail. We have become the things on which we are working. Richard Sennett, The Craftsman The inventive process was often a nonverbal oneHe feels the end of the cane identity