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
The drift The Situationists were also practitioners of a special urban-analytic walking style, the dérive—the “drift”—which Debord described as “a technique of transient passage through varied ambiences. The dérive entails playful-constructive behavior and awareness of psychogeographical effects; which completely distinguishes it from the classical notions of the journey and the stroll.” “In a dérive,” Debord deadpans, “one or more persons during a certain period drop their usual motives for movement and action, their relations, their work and leisure activities, and let themselves be drawn by the attractions of the terrain and the encounters they find there." The dérive joins the free association of surrealism, the LSD of hippiedom, and cinematic montage as tactics for overcoming the fixity of received ideas of order and logic. By putting progress through the city into a state of constant indeterminacy, it represents a schooled “style” of being lost. Michael Sorkin, 20 Minutes in Manhattan PsychogeographyRaindrops leaving an erratic trail psychologymovement