
Examines how (sometimes quasi-) authoritarian central planning fails to deliver the goods, be they increased resources for the state or a better life for the people.
* Seeing Like a State - great overview of how states (and corporations) lose visibility into reality due to the abstraction levels they operate at
* Normal Accidents - all about how things like nuclear reactors, ships and large systems naturally have accidents
* Managing the Unexpected: Resilient Performance in an Age of Uncertainty - great easy read about how high reliability organizations manage complexity and dangerous, high tempo situations.
For example, business intelligence systems provide ways to impose consistent measures on an organisation, which makes the org more legible to executive decision makers, but that consistency also tends to erode local team autonomy and undermine specialist knowledge. This type of tension shows up everywhere once you start noticing it.
Very facinating book.
I once worked at a place where VPs were looking at sprint burndown charts, and asked what happened if the line didn't look a lot like the line expected by JIRA. The telemetry is therefore often a curse, as any metric becomes a target. How many companies today have KPIs about having automated code reviews, which are then ignored by the devs, because said reviews are just wrong on almost everything?
The learnings of Seeing Like A State don't apply just to governments.
People name streets (and other things) for other reasons too, often for internal or local reference. This perspective reduces the meaning of naming to a single focus, like saying we name dogs only to allow our guests to refer to them as needed when visiting our homes. We name things for many reasons, and those reasons are more about endearment and culture building at the local level. I recommend Seeing Like a State by James Scott for more discussion, including about street names, exploring this perspective.