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
What the advancing interface leaves behind I see in the complex structure of any material—biological or geological, natural or artificial—a record of its history, a history of many individual events each of which did predictably follow physical principles. Nothing containing more than a few parts appears full panoplied, but it grows. And as it grows, the advancing interface leaves behind a pattern of structure perfection or imperfection which is both a record of historical events and a framework within which future ones must occur. Matter versus Materials: A Historical View From the head of Jove historygrowthstructure