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 little too something As Irwin had chosen a stairwell for his UCLA installation because it was curious in its banality and innocuousness, Bruce Nauman became interested in corridors and shafts as overlooked and slightly eccentric spaces. He was particularly interested in those that had "a kind of constriction that wasn't natural or was a little too long or a little too something—like the architect just hadn't really thought it out." Michael Auping, Stealth Architecture: The Rooms of Light and Space Merely a building