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
Stands up and hums The ruin [at Marfa] itself, in fact, set the terms for the kinds of solutions Irwin would propose, since its absent roof and floor, and its shockingly wide-open sequences of windows, which overlap and align with one another from different points of view on the site, already presented a rich, thoroughly keyed-up set of perceptual events before Irwin ever considered the project. It was already one of those sites that, in Irwin's words, "stands up and hums" thanks to the rich quality of their perceptual phenomena. Matthew Simms, Robert Irwin: A Conditional Art Economy of line