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
City districts Districts have to help bring the resources of a city down to where they are needed by street neighborhoods, and they have to help translate the experiences of real life, in street neighborhoods, into policies and purposes of their city as a whole. And they have to help maintain an area that is usable, in a civilized way, not only for its own residents but for other users—workers, customers, visitors—from the city as a whole. To accomplish these functions, an effective district has to be large enough to count as a force in the life of the city as a whole. The “ideal” neighborhood of planning theory is useless for such a role. A district has to be big and powerful enough to fight city hall. Nothing less is to any purpose. Jane Jacobs, The Death and Life of Great American Cities Paths, edges, districts, nodes, landmarks