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
One Of Us That’s the primary difference between an axiom like “Curiosity Killed The Cat” and an axiom like “You Are Not Your User. ” The former rings true in common experience. It’s test-able, like striking a tuning fork or dangling a bit of yarn in front of a kitten. The latter is just some stuff that somebody said. Sometimes, axiomatic sayings like “You Are Not Your User” no longer have a who that’s saying them. They cease being an actual instruction, and instead serve as a kind of identity, to identify the person who’s repeating the axiom as One Of Us. The technical term for when an axiom devolves into an ID card is shibboleth: a custom, principle, or belief distinguishing a particular class or group of people, especially a long-standing one regarded as outmoded or no longer important. Dan Klyn, Sermon for WIAD Bristol 2021 understandinggroup.com The Nature of Product identity