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
Irwin Volumes Show image 0 Show image 1 Show image 2 Show image 3 Show image 4 Black Line Volume, String Line-Light Volume, Corridor String Piece, Line Rectangle "The resultant black rectangle was not what you "looked at" – there was actually nothing to focus on – but soon it brought the space into focus with a distinct visual snap. From inside, the light in the area seemed different, more substantial, and the wall color began to shift ambiguously. From outside the area, the tape seemed to lift the plane of the floor upward in your field of vision, and it also made the room seem wider and shallower than it really was." — Roberta Smith Robert Irwin, Robert Irwin: A Conditional Art You are the one that is changed