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
The requirements of economy Economy is the mother of most inventions, not necessity, unless in the sense of poverty and hardship. A requirement for convenience is simply a diluted requirement for ease and economy. It seems to be invariably true that those characteristics which lead people to call a design functional are derived from the requirements of economy and not of use. David Pye, The Nature and Aesthetics of Design Form follows functionEconomy of material and labor function