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
Conversational drawing A skilled draughtsman guides design conversations by selecting and emphasizing details in a way that computer programmes cannot. Ron Slade, author of Sketching for Engineers and Architects and a structural director at WSP in London, calls it “conversational drawing”. He notes how botany field guides are always based on detailed drawings rather than photographs — as much for what they leave out as for what they show. “Extraneous material that might exist in a photograph is eliminated. It may be important to pick out and illustrate particular areas and leave other parts in sketchy or broad outline.” Nick Jones, Back to the Drawing Board Why Sketch?