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
Forces of conflict A pattern which prevents us from resolving our conflicting forces leaves us almost perpetually in a state of tension. For, if we live in a world where work is separated from family life, or where courtyards turn us away, or where windows are merely holes in the wall, we experience the stress of these inner and conflicting forces constantly. We can never come to rest. We are living then, in a world so made, so patterned, that we cannot, by any stratagem, defeat the tension, solve the problem, or resolve the conflict. In this kind of world the conflicts do not go away. They stay within us, nagging, tense…The build-up of stress, however minor, stays within us. We live in a state of heightened alertness, higher stress, more adrenaline, all the time. Christopher Alexander, The Timeless Way of Building Fucking up the world