About a month ago, I told you about the book-reading event where Scott Huler (blog, Twitter, SIT interview) read from his latest book On The Grid (amazon.com). I read the book immediately after, but never wrote a review of my own. My event review already contained some of my thoughts about the topic, but I feel I need to say more, if nothing else in order to use this blog to alert more people about it and to tell everyone "Read This Book".
"I think of myself as a reasonably curious and informed person, and I have visited at least a couple of infrastructure plants, but almost every anecdote and every little tidbit of information were new to me. Scott's point - that we don't know almost anything about infrastructure - was thus proven to me."
...was reinforced when I read the book itself: I don't know anything about infrastructure. But after reading the book I can say I know a little bit, understand how much I don't know, and realize how much more I'd like to know. I bet it was fun watching me as I was reading it, exclaiming on average five times per page "This is so cool", and "Hey, this is neat" and "Wow, I had no idea!" and (rarely) "w00t! Here's a tidbit I actually heard of before" and "Hey, I know where this is!" (as I lived in Raleigh for eleven years, I know the area well).
A few years ago, Scott was just as ignorant about infrastructure as most of us are. But then his curiosity got better of him and he started researching. He would start at his house in Raleigh and trace all the wires and cables and pipes going in and out of the house to see where they led. Sometimes there would be a crew on his street digging into the asphalt and fixing something and he would approach them and ask questions. At other times he would figure out where the headquarters are and who to ask to talk to:
"What Scott realized during the two years of research for the book is that people in charge of infrastructure know what they are doing. When something doesn't work well, or the system is not as up-to-date as it could be, it is not due to incompetence or ignorance, but because there is a lack of two essential ingredients: money and political will. These two factors, in turn, become available to the engineers to build and upgrade the systems, only if people are persuaded to act. And people are persuaded to act in two ways: if it becomes too costly, or if it becomes too painful to continue with the old way of doing things. It is also easier to build brand new systems for new services than it is to replace old systems that work 'well enough' with more more modern ways of providing the same service."
In a sense, this book is a memoir of curiosity as Scott describes his own adventures with a hard-hat, a modern Jean Valjean sloshing his way through the Raleigh sewers, test-driving the public transportation, and passing multiple security checks in order to enter the nearby nuclear plant.
But it is more than just a story of personal awe at modern engineering. Scott weaves in the explanations of the engineering and the underlying science, explains the history and the politics of the Raleigh infrastructure, the historical evolution of technologies underlying modern infrastructure, and illustrates it by comparisons to other infrastructures: how does New York City does that, how did Philadelphia did it 50 years ago, how did London 500 years ago, how about Rome 2000 years ago?
"What is really astonishing is how well the systems work, even in USA which has fallen way behind the rest of the developed world. We are taking it for granted that the systems always work, that water and electricity and phone and sewers and garbage collection and public transportation always work. We get angry on those rare occasions when a system temporarily fails. We are, for the most part, unprepared and untrained to provide some of the services ourselves in times of outages, or to continue with normal life and work when a service fails. And we are certainly not teaching our kids the necessary skills - I can chop up wood and start a wood stove, I can use an oil heater, I know how to slaughter and render a pig, how to get water out of a well, dig a ditch, and many other skills I learned as a child (and working around horses) - yet I am not teaching any of that to my own kids. They see it as irrelevant to the modern world and they have a point - chance they will ever need to employ such skills is negligible."
And this brings me to the point where I start musing about stuff that the book leaves out. As I was reading, I was constantly hungry for more. I wanted more comparisons with other cities and countries and how they solved particular problems. I wanted more history. I wanted more science. I wanted more about political angles. But then, when I finished, I realized that a book I was hungry for would be a 10-tome encyclopedic monograph and a complete flop. It is good that Scott has self-control and self-discipline as a writer to know exactly what to include and what to leave out. He provides an excellent Bibliography at the end for everyone who is interested in pursuing a particular interest further. His book's homepage is a repository for some really cool links - just click on the infrastructure you are interested in (note that "Communications" is under construction, as it is in the real world - it is undergoing a revolution as we speak so it is hard to collect a list of 'definitive' resources - those are yet to be written):
What many readers will likely notice as they go through the book is that there is very little about the environmental impacts of various technologies used to ensure that cities function and citizens have all their needs met. And I think this was a good strategy. If Scott included this information, many readers and critics would focus entirely on the environmental bits (already available in so many other books, articles and blogs) and completely miss what the book is all about - the ingenuity needed to keep billions of people living in some kind of semblance of normal life and the interconnectedness that infrastructure imposes on the society, even on those who would want not to be interconnected:
"There are people who advocate for moving "off the grid" and living a self-sufficient existence. But, as Scott discovered, they are fooling themselves. Both the process of moving off the grid and the subsequent life off the grid are still heavily dependent on the grid, on various infrastructure systems that make such a move and such a life possible, at least in the developed world."
My guess is, if there's anyone out there who could possibly not like this book, it will be die-hard libertarians who fantasize about being self-sufficient in this over-populated, inter-connected world.
At several places in the book, Scott tries to define what infrastructure is. It is a network that provides a service to everyone. It has some kind of control center, a collection center or distribution center. It has a number of peripheral stations and nodes. And there are some kinds of channels that connect the central place to the outside stations and those stations to the final users - every household in town. There is also a lot of redundancy built into the system, e.g., if a water main breaks somewhere, you will still get your water but it will come to you via other pipes in surrounding streets, with zero interruption to your service.
Scott covers surveying of land, stormwater, freshwater, wastewater, roads, power, solid waste, communications (phone, broadcast media, internet) and transportation (e.g., public transportation, trains, airplanes). These are the kinds of things that are traditionally thought of as 'infrastructure'. But aren't there other such systems? I'd think security has the same center-spokes model of organization as well: police stations and sub-stations (distribution centers) that can send cops out wherever needed (distribution channels), with potential criminals brought to court (processing centers) and if found guilty placed in prison (collection center). Similarly with fire-departments. Ambulances are just the most peripheral tentacles of the health-care infrastructure. The local-county-state-federal political system is also a kind of infrastructure. So is the military. So is the postal system. So is the food industry and distribution.
Thinking about all of these other potential examples of infrastructure made me realize how many services that require complex infrastructure undergo cycles of centralization and decentralization. For transportation, everyone needed to have a horse. Later, it was centralized into ship, railroad, bus and airline infrastructures. But that was counteracted by the popularity of individually owned cars. And of course taxis were there all along. And as each decade and each country has its own slight moves towards or away from centralization, in the end a balance is struck in which both modes operate.
You raised your own chickens. Then you bought them from mega-farms. Now many, but not most citizens, are raising their own chickens again. It is not feasible - not enough square miles on the planet - for everyone to raise chickens any more. But having everyone fed factory chicken is not palatable to many, either. Thus, a new, uneasy balance.
Nowhere is this seen more obviously today as in Communications infrastructure. We are in the middle of a big decentralization movement, away from broadcast (radio, TV and yes, newspaper industry infrastructure with its printing presses, distribution centers and trucks) infrastructure that marked about half of 20th century, and forward into something more resembling the media ecosystem of the most of human history - everyone is both a sender and a receiver, except that instead of writing letters or assembling at a pub every evening, we can do this online. But internet is itself an infrastructure - a series of tubes network of cables and it is essential not to allow any centralized corporation to have any power over what passes through those cables and who gets to send and receive stuff this way.
Finally, as I was reading the book I was often wishing to see photographs of places or drawings of the engineering systems he describes. As good as Scott is at putting it in words, there were times when I really wanted to actually see how something looks like. And there were times when what I really wanted was something even more interactive, perhaps an online visualization of an infrastructure system that allows me to change parameters (e.g., amount of rainfall per minute) and see how that effects some output (e.g., rate of clearing water off the streets, or speed at which it is rushing through the pipes, or how it affects the water level of the receiving river). That kind of stuff would make this really come to life to me.
Perhaps "On The Grid" will have an iPad edition in the future in which the text of the book is just a beginning of the journey - links to other sources (e,g., solutions around the globe, historical sources), to images, videos, interactive visualizations and, why not, real games. After all, it is right here in Raleigh that IBM is designing a game that allows one to plan and build modern infrastructure - CityOne. These two should talk to each other and make something magnificent like that.
Cross-posted from Science In The Triangle.
The small images are thumbnails - click on each to see the whole picture, full-size.