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
Designed to be ruins I don't want to talk here about the grand designs of the past – the sort of thing one finds in majestic cities, in palaces and temples; the sorts of layouts that brought a friend of mine to sum up his first impression of Washington D.C. by saying, "The place seems to be designed to be ruins." Ursula M. Franklin, The Real World of Technology To build a follyWittgenstein's Mistress urbanism