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
What the painting was not about That is why for many years Irwin declined to allow his work to be photographed, because the image of the canvas was precisely what the painting was not about. Indeed, the problem is even more complicated than that. For in a very real sense the achievement of these paintings was in their making, and the finished canvas at one level is only an incidental relic, a fossil of that original process of discovery: not only do you have to be present before these paintings in order to experience them, it may be that you have to have made them as well. Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees Only a mind opened to the quality of things photographyimages