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
Only in terms of other things No legislation could prevent the making of verbal pictures: God walks in the garden, He stretches out His arm, His voice shakes the cedars, His eyelids try the children of men. To forbid the making of pictures about God would be to forbid thinking about God at all, for man is so made that he has no way to think except in pictures. But continually, throughout the history of the Jewish-Christian Church, the voice of warning has been raised against the power of the picture-makers: “God is a spirit”, “without body, parts or passions”; He is pure being, “I AM THAT I AM”. The fact is, that all language about everything is analogical; we think in a series of metaphors. We can explain nothing in terms of itself, but only in terms of other things. Dorothy Sayers, The Mind of the Maker Metaphors We Live ByYou only understand something relative to something you already understand metaphoranalogy