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
A fresh focus of power The demand for “originality”—with the implication that the reminiscence of other writers is a sin against originality and a defect in the work—is a recent one and would have seemed quite ludicrous to poets of the Augustan Age, or of Shakespeare’s time. The traditional view is that each new work should be a fresh focus of power through which former streams of beauty, emotion, and reflection are directed. This view is adopted, and perhaps carried to excess, by writers like T. S. Eliot, some of whose poems are a close web of quotations and adaptations, chosen for their associative value, or like James Joyce, who makes great use of the associative value of sounds and syllables. Dorothy Sayers, The Mind of the Maker On TheftThe signature novelty