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
Induced demand Every attempt to cul-de-sac city streets, to change traffic patterns in favor of pedestrians, or to narrow street ends is met with the same howl of protest from the authorities: this will increase congestion because urban traffic is a zero-sum game. Any reduction in volume in one place in the city will inevitably be accompanied by a rise in traffic somewhere else. This claim is fallacious: the true corollary is the opposite. In case after case, a reduction of the space available for vehicular traffic has simply resulted in the reduction of traffic overall. Michael Sorkin, 20 Minutes in Manhattan Like trying to cure obesity by loosening your belt transportation