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 Abode of Fancy The name, Abode of Fancy, implies a structure created to meet some individual artistic requirement. The tea room is made for the tea master, not the tea master for the tea room. It is not intended for posterity and is therefore ephemeral. The idea that everyone should have a house of his own is based on an ancient custom of & the Japanese race, Shinto superstition ordaining that every dwelling should be evacuated on the death of its chief occupant. Perhaps there may have been some unrealized sanitary reason for this practice. Another early custom was that a newly built house should be provided for each couple that married. It is on account of such customs that we find the Imperial capitals so frequently removed from one site to another in ancient days. Okakura Kakuzō, The Book of Tea Poems of an Indian summerEach ruler commissioned his own gardenIse Shrines, Nagoya, 685–Present home