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
There it is again Apparently architecture does the same job as set design, "it creates units of environment, atmosphere, or events"—whatever you wish to call them—but with more weight, carrying more material, slower. This is why it can raise the curtain more times and repeat "there it is again" for longer. Perhaps for this and other reasons there are periods in the history of architecture in which stage design or the folly, for example, have been an effective field of experimentation for serious architects. Smiljan Radić, The Circus Follies architecture