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
But then the knoll was gone These banks were making the same mistake as a family I know who bought an acre in the country on which to build a house. For many years, while they lacked the money to build, they visited the site regularly and picnicked on a knoll, the site’s most attractive feature. They liked so much to visualize themselves as always there, that when they finally built they put the house on the knoll. But then the knoll was gone. Somehow they had not realized they would destroy it and lose it by supplanting it with themselves. Jane Jacobs, The Death and Life of Great American Cities 104. Site Repair