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
Repair Within the larger language, it is impossible for any act not to help repair the larger whole. It is impossible for any act of building to remain an isolated act: it always becomes a portion of the flux of acts which is helping to maintain the whole. Even the laying of a brick, to mend a wall, will not only be used to mend that wall, but will be used to help repair the seat, the terrace, or the fireplace which that wall helps to form. Christopher Alexander, The Timeless Way of Building 104. Site Repair repair