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
Eyes on the street You can’t make people use streets they have no reason to use. You can’t make people watch streets they do not want to watch. Safety on the streets by surveillance and mutual policing of one another sounds grim, but in real life it is not grim. The safety of the street works best, most casually, and with least frequent taint of hostility or suspicion precisely where people are using and most enjoying the city streets voluntarily and are least conscious, normally, that they are policing. Jane Jacobs, The Death and Life of Great American Cities To deter crime safety