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
Sonorisms I the authenticity of the gesture as if the air had taken on substance representation and re-presentation a first order of presence this painterly game of pick-up sticks Irwin's "fetish finish" questions all of whose possible answers would never exhaust them the art is what has happened to the viewer an art of things not looked at a dialogue of immanence the information that takes place between things your house is the last before the infinite his "project of general peripatetic availability" that shiver of perception perceiving itself a desert of pure feeling Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees PhonaestheticsArchitectural dark matter wordseuphony