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
Most cities were mostly built by improvisation In Architecture Without Architects, Bernard Rudofsky documented the ways in which most cities were mostly built by improvisation, following no consistent formal design. Building was added to building, street to street, their forms adapting to different site conditions in the process of extension. Rudofsky thought that this hidden order is how most settlements of poor people develop and that the work of improvising street order attaches people to their communities, whereas 'renewal' projects, which may provide a cleaner street, pretty houses, and large shops, give the inhabitants no way to mark their presence on the space. Richard Sennett, The Craftsman I am hereNon-architects urbanism