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
Things that shine and glitter We find it hard to be really at home with things that shine and glitter. The Westerner uses silver and steel and nickel tableware, and polishes it to a fine brilliance, but we object to the practice. On the contrary we begin to enjoy it only when the luster has worn off, when it has begun to take on a dark, smoky, patina. Jun'ichirō Tanizaki & Thomas J. Harper, In Praise of Shadows The dignity of ageThe economic value of old buildings flawsaesthetics