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 Fluorescents Show image 0 Show image 1 Show image 2 Show image 3 Show image 4 In order: Kenny Price, Blue Lou, Legacy, Fourfold, Niagara. Irwin has explained that he decided to use the fluorescent tubes in the "dumbest" way possible, but, as one critic cautioned, "dumb, it turns out, has a special meaning for him: It's a form so simple that you end up not paying attention to it as a form." Irwin's interest was, rather, in the range of light, color, reflection, and shadow interaction made possible by combining tubes with different hues and finishes by wrapping them with theatrical gels. Robert Irwin, Robert Irwin: A Conditional Art Interaction of Color colorlight