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
1º2º3º4º Because the approach to the room is along a long corridor, the attentive visitor might at first think that three light squares had been affixed to the windows or, as one gradually came closer, that the tinting of the windows had simply been removed in these three lighter near-square areas. Davies continues: "only at this point do the other senses kick in. The visitor begins first to hear and smell the ocean and then to actually feel the outside air entering the gallery; this sensory experience is in complete contradiction to the faulty first impression." Robert Irwin, Robert Irwin: A Conditional Art The inhumanity of contemporary architecture senseswindows