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
From the head of Jove A complex structure is a result of, and to a large extent a record of, its past. Though a proton and an electron may, as a pair, be able to spring full-panoplied from the head of Jove, more complex things cannot, or at least do not. Everything complicated must have had a history, and its internal structural features arise from its history and provide a specific record of it. One might call these structural details of memory “funeous,” after the unfortunate character in Borge’s story “Funes the Memorious” who remembered everything. The Interpretation of Microstructures of Metallic Artifacts What the advancing interface leaves behind memorytimestructurematerial