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
Controlled environments “Controlled environments” are another of modernism’s great obsessions. Extravagant amounts of energy are spent to keep buildings—as well as skyway systems, shopping malls, and domed stadia—at a constant temperature year-round via entirely mechanical means. The folly is not simply a touchy-feely isolation from the authenticities of nature, which can admittedly be cruel, but a larger disciplinary presumption that seeks to extend the centralized authority (central air, central government) of power ever more comprehensively. It is possible that this particular hubris may have pushed Gaia to the tipping point. Michael Sorkin, 20 Minutes in Manhattan At a uniformly comfortable termperatureFascination with control sustainabilitycontrol