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
You are the one that is changed I tilt the room just enough, the space just enough that you may not be able to use your normal mode of placing yourself in that space, forcing you for one second to make a perceptual read and become aware that you are the perceiver and that all information comes through that perceptual act and that when you walk out of there, ...if you take that with you, you will begin to see things everywhere around you and that you are the one that is changed and you are there and that is what changed things. Robert Irwin, Robert Irwin: A Conditional Art Irwin Volumes