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
Deep Interlock Forms which have a high degree of life tend to contain some type of interlock – a “hooking into” their surroundings – or an ambiguity between element and context, either case creating a zone belonging to both the form and to its surroundings, making it difficult to disentangle the two. The interlock, or ambiguity, strengthens the centers on either side, which are intensified by the new center formed between the two. Christopher Alexander, The Nature of Order The versatility of flat surfacesStrength from both mass and form168. Connection to the EarthInterlockingProtected, yet tuned in naturearchitecture