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
Unfolding In short, the architect is responsible for building construction, is watching the building unfold continuously, and is making ongoing modifications as it becomes clear from each given stage, what modifications and changes should be made at each moment. And this is all to be done within a management framework that controls budget and cost very tightly. Christopher Alexander, The Battle for the Life and Beauty of the Earth In terms which must be altered