Showing posts sorted by relevance for query Henry Petroski. Sort by date Show all posts
Showing posts sorted by relevance for query Henry Petroski. Sort by date Show all posts

Thursday, July 14, 2011

The Essential Engineer by Henry Petroski

Petroski, Henry. The Essential Engineer: Why Science Alone Will Not Solve Our Global Problems. New York: Vintage, 2010.

Policy makers seem to love science. I can see why. Science provides a sense of specificity, certainty and consensus. It contrasts with the vagueness, variability and competition that policy makers usually have to deal with. That is more like the world engineering.

This interrelation of policy-making, science and engineering, especially the latter two, is the subject of Henry Petroski’s book, The Essential Engineer. In particular, Petroski emphasizes the important, and often overlooked, role of engineering is solving pressing problems.



I doesn’t help that people conflate science and engineering, especially by thinking of engineering as branch or application of science. Petroski is clear about the differences. Science is about increasing knowledge. Engineering is about invention. Sometimes scientists do engineering, especially when they create a devise or process to help them in their work of discovery. Sometimes engineers do science, especially when their engage in research and experimentation to gain a better understanding or problems that are not well understood.

The movement of knowledge from science to engineering practice is well understood. Petroski describes how this became ingrained in American research and development policy. Engineering often precedes science and engineers often must invent solutions in areas that are not well understood by science. Galileo’s improvements to the telescope made possible his advancements in astronomy. The science of thermodynamics grew almost entirely out of the desire to understand steam engines, which engineers had been building and improving in the absence of scientific understanding.

This misunderstanding exacerbated by our culture and education. Policy elites and scientist generally have no education in engineering. As an undergraduate studying engineering, I took science classes with students majoring in the sciences. I took classes in political science, economics and other social science and business-oriented classes with students majoring in those fields. I would have been greatly surprised to find in one of my engineering classes a student who wasn’t majoring in engineering.*

Petroski does not try to bring down science. He’s a civil engineering professor at a sizeable university, so he has probably spent quite a bit of time doing science. He does distinguish how science is helpful, mainly as a warning. Science can help us identify and define problems and assess the risks involve. When we begin to devise solutions to those problems, especially when there is no definitive solution and judgment is needed to way the pros and cons of multiple possible answers, we are moving into engineering.

The Essential Engineer is not a technical book. It for anyone who may have an interest in the role of technology in addressing our problems, especially larger societal problems. Petroski draws illustrations from current events and history (he is a professor of history as well as engineering). The book is enlivened with a storytelling feel.

* There were exceptions. I took a course in food processing that was dual-listed in agricultural engineering and food science. It was a required course for both disciplines. Electrical engineering students almost automatically minored in math, and some clever and ambitious students double-majored in those subjects. With a little better planning, I could have swung a minor in agricultural economics, and I almost wish I had. When I got into wastewater engineering, I wished I had taken more microbiology. My pursuit of additional education lead to a graduate degree in public administration. Government agencies have been employers or clients most of my career. It is common for engineers to get a masters degree in business, especially as they become managers.

Henry Petroski also wrote Paperboy.

If you’re interested in this book, you may also be interested in
The Ancient Engineers by L. Sprague de Camp
The Big Necessity by Rose George
Newton and the Counterfeiter by Thomas Levenson

Related News
Avoiding Doomsday: New Ideas for Deflecting Killer Asteroids
Future Asteroid Mission: Mission Impossible?
Potential meteor menace overstated

Tuesday, December 21, 2010

Paperboy by Henry Petroski

Petroski, Henry. Paperboy: Confessions of a Future Engineer. New York: Knopf, 2002.

Henry Petroski is an engineering professor who is well known for his books on engineering and technology. Paperboy is a memoir of his boyhood.

This memoir is a reflection of the times, the 1950s, as well as the author’s life. It shows a microcosm of a nation recovering from World War II and gearing up for the space race. The paperboys of New York weren’t interested in reading the newspapers they delivered, so they weren’t consciously aware of the social forces at work around them. (Even so, Petroski uses headlines from the Long Island Press to show what was going on at the time.) A boy with Petroski’s talents might have gone into any number of things, but with Sputnik overhead, government policy and watchful teachers nudged him into engineering. It was a good fit.

Petroski doesn’t leave technology completely out of the picture. As a paperboy, he had to master the art of folding and flipping papers. He assembled and maintained his own bicycle. He watched his orderly uncle, an accountant, put together exactly what he needed to build an attic closet with no waist.

Young Petroski had many traits that would have made engineering attractive to him: curiosity about how things work, mechanical aptitude, facility with mathematics, some perfectionism, more pragmatism, ability to think both concretely and abstractly, appreciate that things are made and making involves choosing. I have known and worked with many engineers in my career in that profession and nearly all of them share at least a few of these traits with Petroski.

A particular part of Petroski’s school experience stands out to me because it illustrates how real life is different from a story. His high school algebra teacher, Mr. Duncan, took an immediate dislike to him, apparently because it picked up on algebra so easily. Duncan began to call Petroski “Herman Peterson,” provoked him and sent him out into the hall. The budding engineer sat in the hall, following the lessons through the door, and remaining the leading student in the class. This hardship continued until Petroski advanced into upper-class math courses. A story probably would have had some satisfying resolution, but real life experience involved just moving on.

In one section of his memoir, Petroski discusses newspaper titles. It’s the kind of list-making thing many engineers are prone to do. The weekly paper in my hometown was the Bloomfield Vindicator. I have never heard a name for newspaper that was cooler than Vindicator. I’m reminded by it of those show that were popular in the 1980s about a nameless stranger who comes into town to bring justice to oppressors of the downtrodden like The Equalizer, Stingray, and The Pretender (which may have been from the 1990s). A syndicate combined the Vindicator with another publication and given it the unimaginative title of North Stoddard Countian.


If you’re interested in this book, you may also be interested in
Copernicus’ Secret by Jack Repcheck
Descarte’s Secret Notebook by Amir D. Aczel
The Invention of Air by Steven Johnson
Newton and the Counterfeiter by Thomas Levenson
The Science of Leonardo by Fritjof Capra

Wednesday, August 31, 2011

200 Books Reviewed on Keenan’s Book Reviews

First Time Reviews

365 Thank Yous by John Kralik
The Abolition of Man by C. S. Lewis
Acts
American Splendor by Harvey Pekar
Batman created by Bob Kane

Caves of Steel by Isaac Asimov
Change Your Brain Change Your Body by Daniel G. Amen
The Checklist Manifesto by Atul Gawande
The DC Comics Guide to Writing Comics by Dennis O’Neil
The Drunkard’s Walk by Leonard Mlodinow

The Essential Engineer by Henry Petroski
Exodus
Finding Your Writer’s Voice by Thaisa Frank & Dorothy Wall
God’s Secretaries by Adam Nicolson
The Gospel of John

The Gospels
Have a New You by Friday by Kevin Leman
Histories and Fallacies by Carl R. Trueman
How to Get Control of Your Time and Your Life by Alan Lakein
How to Read Literature Like a Professor by Thomas C. Foster

How to Write & Present Technical Information by Charles H. Sides
How to Write Horror Fiction by William F. Nolan
I Can Make You Thin by Paul McKenna
In the Beginning by Alister McGrath
Jonah Hex created by John Albano and Tone DeZuniga

Judge Dredd created by John Wagner and Carlos Ezquerra
King James Bible
Little Shifts by Suzanna Beth Stinnet
Love and Respect by Emerson Eggerichs
Newton and the Counterfeiter by Thomas Levenson

Numbers
On Becoming a Leader by Warren Bennis
Our Cancer Year by Harvey Pekar and Joyce Brabner
Paperboy by Henry Petroski
The Pilgrim’s Progress by John Bunyan

The Procrastination Equation by Piers Steel
Romans
Scott Pilgrim’s Precious Little Life by Bryan Lee O’Malley
Scott Pilgrim vs. the World by Bryan Lee O’Malley
The Sherlockian by Graham Moore

The Ten-Cent Plague by David Hajdu
Thanks! by Robert A. Emmons
True Blood by Charlaine Harris
The Ultimate Weight Solution by Phil McGraw
Vital Friends by Tom Rath

Walk Away the Pounds by Leslie Sansone
War Against the Weak by Edwin Black
Wide as the Waters by Benson Bobrick
Writing for Comics with Peter David
Zorro created by Johnston McCulley

Additional and Expanded Reviews

The Holy Bible
Into the Depths of God by Calvin Miller
The Road to Serfdom by F. A. Hayek
Simple Pictures are Best by Nancy Willard, illustrated by Tomie de Paola

Continuation of list of 200 books reviewed

First 25 Reviews
Reviews 26-50
Reviews 51-75
Reviews 76-100
Reviews 101-150

Friday, December 21, 2012

STEM Books

I’ve reviewed 39 STEM-related books (and counting).  STEM is an acronym for science, technology, engineering, and mathematics.  As you may have seen in the news, there is a push to improve STEM education, interest students in STEM fields, and grow the number of workers in these fields.  The idea is that these will be the skills needed by workers of the future.  If you’re a STEM educator or a student considering a career in STEM fields, you might like to take a look at some of these books.

I’ll confess that I’m not an educator, but I think most of these books will be accessible to high school and college students, and a few to middle school students.  The list is also a reflection of my career and interests in engineering, public health, policy, and history.  Even with these biases, I think it is a good list for someone looking for STEM-related books.


I was fascinated by robots as a kid.  I enjoyed reading Isaac Asimov’s robot stories.  I longed for the Omnibot 2000 in the Sears Wishbook.

Robots have come a long way.  In How to Build an Android, David F. Dufty describes the short strange life of a very complex robot made to look and talk like science fiction author Philip K. Dick.  The robot had a very sophisticated and lifelike head and complex artificial intelligence.  As with most complex things, it was the work of many people who had to solve a lot of problems.

If you’re interested in robotics, this is an interesting nontechnical book.  In addition, you’ll get introduced to some freaky sci-fi.  You may even get as (somewhat) legitimate reason to use the word “Dickhead” (capitalized, it refers to a fan of PKD, so don’t go using it on anyone).



The Interstate highway system in the United States is one of the most enormous structures built.  Some of the prospective STEM students who read this may actually be younger than the Intestate system, though in some sense it is never complete because it needs constant repair and maintenance.  The Interstates were completed in the 1990s, but the Federal-Aid Highways go back to 1916.

Earl Swift wrote an accessible history of the Interstates in The Big Roads.  If you interested in automobiles or transportation, it’s a good read.



Deborah Cadbury describes seven wonders of engineering in Dreams of Iron and Steel.  It covers almost a century of history, but many of the events are concentrated in the Victorian Era.  That was a time of great technological innovation.

Though the book is history, many of the structures still stand.  Railways, the Brooklyn Bridge, the Suez and Panama Canals, and Hoover Dam stand testament to an age of big engineering.



Though the memory of Professor Wragg’s sneer prompts me to not make this confession, part of my interest in science and technology came from comic books.  Iron Man was cool.  Spider-Man’s web shooters were very cool.  Superhero comics are full of fantasy, admittedly, but the strange, unrealistic science and technology they depict have inspired many to study STEM in reality.

Physicist John Kakalios uses examples from comic books to explore real physics in The Physics of Supeheroes.  Sometimes comics get there science right.  Even when they get it wrong, it can be instructive.  If you know what people are talking about when they refer to the “New 52,” you may find this book to be a great introduction to physics.



Here is another confession: I’m not especially interested in math.  I endured a lot of math classes to study engineering.  Reading David Acheson’s 1089 and All That did not require such endurance.  For one reason, it is a short book.  For another, Acheson doesn’t expect his readers to be mathematicians; it is enough to follow the outline of the math he discusses.

I recommend this book because so many people have a fear of math.  1089 can be followed by many high school students and older folks with math phobias.  Just take a deep breath, relax, and follow along as well as you can.  You’ll see that math can be interesting, useful, and even beautiful in a way.



Judith St. George’s The Brooklyn Bridge is a short history of and iconic bridge.  Written for the bridge’s 100th anniversary, it is also the story of the engineers who sacrificed life and health to see it completed: John Roebling and his son Washington.  John Roebling was a German immigrant who built many suspension bridges and owed a wire-making business.  He gave his son and extraordinary education in bridge engineering for the time, and before beginning work on the Brooklyn Bridge he served as an officer in the Union Army during the Civil War.

Why should a cutting-edge STEM student read about a bridge that is almost 130 years old?  It’s because we still use and rely on very successful, centuries old technologies.  Improving and rebuilding our infrastructure will be an important part of our economy.  As recently as 2010, New York City and the federal government committed $500 million to repair and repaint the Brooklyn Bridge.



STEM lumps together science, technology, engineering, and mathematics.  Is there a difference between science and engineering?  Is it important?

Henry Petroski, a professor of civil engineering and history and author of The Essential Engineer, believes there is an important difference.  At heart, science is about increasing knowledge.  Engineering is about invention.  Of course, new knowledge makes new invention possible.  Just as often, though, engineering runs ahead of science.  Sometimes science didn’t advance until someone invented the instruments to conduct new observations and experiments.  The invention of the microscope made possible the science of microbiology.  Steam engines were built and greatly improved before we had a modern scientific understanding of thermodynamics.  In fact, thermodynamics was to a large extent born out of desire to understand steam engines. In this sense, it is an engineering science (study of manmade things) as much as a natural science (study of natural things) or branch of physics.

Petroski’s focus in the book is the importance of engineering to policymaking, where it is often overshadowed by science.  Policy, science, and engineering play off of each other a lot.  Most of my career as an engineer has been related to government, policy, and regulatory compliance.



The Ghost Map by science writer Steven Johnson is the story of the birth of epidemiology.  Epidemiology is a medical science that uses statistics to help us understand how diseases operate in a population.  Using various statistical and geographic tools, long before we had computers and GIS, physician John Snow demonstrated that cholera, once a recurring plague that wiped out hundreds of thousands of people in some outbreaks, was a waterborne disease.  This understanding, initially met with much skepticism, allowed officials to intervene to prevent the spread of the disease.  For those who say of their math classes, “I’ll never us this,” here is a case where math (and science and policy) were used to make a great difference.



It is not much publicized today that the Lewis and Clark expedition of 1804 to 1806 had a partly scientific mission.  Captains Lewis and Clark were charges with bringing back samples of the flora, fauna, and culture of the western territories.  It was also hoped that they would find a water passage to the Pacific Ocean.  In Undaunted Courage, Stephen Ambrose writes about the scientific mission as well as the policy, diplomacy, and commercial hopes the expedition carried.

Of course, what attracts most people to the Lewis and Clark expedition is that it was a great adventure.  There is a place in STEM fields for thoughtful adventurers and explorers. 



A list like this deserves something strange, creepy, and more fun than you care to admit.  Right now, thousands of very young future STEM workers are catching bugs and snakes, breaking their toys to see what is inside, or staring into space with a weird expression of vacancy and concentration.

Jan Bondeson’s Buried Alive is not a morbid book.  It is sometimes humorous, especially in consideration of topic.  From a STEM point of view, Bondeson shows how knowledge accumulates over time.  The fears and activities of our forefathers may seem strange to us, but they sometimes made sense in light of what they knew.  Buried Alive doesn’t simply play off our fascination with the grotesque and death, though the book might not have been written if we lacked that fascination, I think it reminds us to approach our ancestors with a touch of grace and humility.  Maybe our progeny will show us the same courtesy.


If you’re looking for something for a younger student, check out this post→ from Joanne Loves Science or these recommendations→ from STEM Friday.  By the way, I also write about engineering, infrastructure and the environment at Infrastructure Watch.

Google

Tuesday, November 20, 2012

Dickhead Roboticists

It appears that the fields of computer science and robotics attract a lot of Dickheads.  By that I mean fans of science fiction author Philip K. Dick.  Psychology researcher David F. Dufty is acquainted with a few of these fans, academics, engineers, and artists, who undertook the strange challenge of building an android simulacrum of their hero.  He tells their story in How to Build an Android.


Dick is possibly the best choice for an author to imitate in robotic form.  He is well known for his story Do Androids Dream of Electric Sheep?, which was the basis of the movie Blade Runner.  The essence of the story is that robots have become so sophisticated, intelligent, and lifelike that it is almost impossible to distinguish them from real humans.  They blow away a Turing test, and the latest models can only be identified through a test that detects their carefully disguised lack of empathy; Dick thought empathy was an essentially human trait that may not be copied by computers.  The hero of Do Androids Dream must track down and destroy these nearly human machines.


Throughout this story and others, Dick explored identity and the shrinking difference between human and machine.  People suspect themselves to be androids, androids are programmed to believe they are human, and both have false memories that they cannot distinguish from reality.  A realistic android that interacted with people in conversation seemed like a natural fit with Dick.


Of course, the project had practical implications.  It required a lifelike interface.  Artist and robot maker David Hanson believes the face is a natural way for people to interact with each other and potentially with technology.  He has made a succession of realistic robotic heads that can imitate human expression.  The PKD robot was backed by artificial intelligence developed by researchers at the University of Memphis, particularly Andrew Olney, that allowed it to understand speech and construct responses based on things Dick had said and written in life.

To top it off, something happened in the brief life of the android that would have been well suited for one of Dick’s stories.  They lost Dick’s head.  Presumably it is still out there.  It may be in some airline warehouse.  It may be on the mantle of some thief, or some flummoxed buyer of a lot of abandoned baggage.  If someone has it, they haven’t been talking about it.

The big question of the book is how do we interact with technology?  What will it look like in the future?  We will be increasingly able to make machines that at least seem intelligent and look human.  Hanson thinks that is the way to go.  The Memphis scientists and engineers, and many other like them, continue to work on interfaces capable of increasingly sophisticated and seamless interactions with people.  Are we on a trajectory from Siri to Jacosta to C-3PO to R. Daneel Olivaw?  Are androids just what we need to make technology what we need or are they too creepy?

Dufty doesn’t pass judgment.  The PKD was an interesting piece of technology with and interesting history that raises a lot of questions about what machines can be.  Even as advance and capable as the PKD android was, it had a lot of limitations.  It could carry on a conversation, in a quiet room with a patient partner, but it did little else and its responses varied from the seemingly real thing to nonsense.

Personally, I don’t think we need, nor do I want, computers with faces.  I would be pleased if I could get my Windows 8 tiles to work.  I do think the way we interact with technology is important, especially that we are able to get feedback and other information from technology in ways that helps us understand what is going on and respond intelligently.

If you’re interested in this book, you may also be interested in

Dufty, David F.  How to Build an Android: The True Story of Philip K. Dick’s Robotic Resurrection.  New York: Henry Holt, 2012.

Google

Saturday, October 31, 2015

Professional Amateur by T. A. Boyd

Charles F. Kettering’s legacy as a philanthropist is memorialized in the names of the institutions he supported such as the Kettering Foundation and the Memorial Sloan-Kettering Cancer Center. As an engineer, I’m more familiar with is reputation as an inventor and innovator, especially in automotive engineering.

Kettering’s associate, T. A. Boyd, memorialized him in the biography Professional Amateur. I think the title is intended to convey Kettering’s humility and determination to not let expertise or established knowledge get in the way of progress. As an engineer, and arguably a scientist, Kettering was devoted to experimentation.

As with others of his era (he was born in 1876), Kettering’s education was not traditional by current standards. After graduating high school, he began teaching in one-room schoolhouses in Ohio such as the one he had attended. He later attended the College of Wooster, studying Greek with an eye toward becoming a pastor, and eventually graduated from the Ohio State University with a degree in electrical engineering. Problems with his eyes caused interruptions in his formal education.

Kettering valued his school experience, but he also valued his practical experience. He got a job installing poles for a telephone company and worked his way into installing lines and switchboards. He and friends undertook amateur experiments in chemistry and electricity. Even as a child he took great interest in nature.

After introducing us to his early life, the book turns to his career as an inventor and research engineer. He established what is now Delco, which he sold to General Motors. He had a long career leading the research efforts at GM. The final chapters of the book describe Kettering’s views on business and education and his career as a public speaker.

Kettering met his wife, Olive, while working for a rural telephone company. Their son, Gene, followed his father into engineering and eventually had a successful career in designing and building diesel-electric locomotives a General Motors.

Boyd was a friend of Kettering, who was still alive when Professional Amateur was published. Needless to say, the book is very complimentary to its subject. Few faults are attributed to the man, except that Kettering is depicted as being so absorbed in his research that he would overlook social conventions like keeping a nice suit clean, entertaining guests, or remembering the purpose of his appointments. The research engineer left his business affairs mostly in the hands of trusted partners so he could concentrate on the work that interested him, though Boyd’s depiction indicates Kettering was shrewd about business.

I don’t think the book is intended for children, but it is written in simple and direct style that might be accessible to many young readers. It was published in 1957, so more recent or thorough biographies may be available. For instance, Kettering introduced tetraethyl lead to gasoline as a way to reduce knock and improve fuel efficiency. Though it was considered safe at the time (as Boyd points out), the lead emissions from automobiles has be reevaluated sense and we no longer use leaded gasoline. The book was written before anyone was seriously aware of or concerned about this issue, so it does not consider it.

If you’re interested in this book, you may also be interested in


Boyd, T. A. Professional Amateur: The Biography of Charles Franklin Kettering. New York: E. P. Dutton & Co., 1957.

Monday, September 2, 2013

Dog Days by Dave Ihlenfeld

Dog Days is a memoir by fellow University of Missouri alumnus Dave Ihlenfeld about his year as a Hotdogger. A Hotdogger is one who drives one of Oscar Mayer’s Wienermobiles.

As you expect from a memoir, the focus is personal recollections. To me, this was the least interesting part of the book. I have little interest in reading about a young guy falling in love with half the pretty women he meets and trying to get laid. Too many television shows and films are already built on that premise. Ihlenfeld writes for television now, so he may have been playing to a strength. There is a little bit of a coming of age story; a year in the Wienermobile calls for resourcefulness.

There is a little history of the Wienermobile in the book. I found this to be some of the most interesting stuff. If you have only a casual interest in the Wienermobile, don’t worry. The history parts are short an dispersed throughout the book. It is not the focus of the book, but it adds something good. Sure, Hotdogger is a silly job in some ways, but it is connected to a long history of successful marketing.

The book is a little bit travelogue. I wish there could have been more of this. I don’t normally read travel books, but the context of it made me open to reading about the destinations. Perhaps the problem is that too many of destinations were county fairs, Walmarts and grocery stores. You can only go so far to make them interesting, especially when your memory of the is clouded by exhaustion (and I suspect the occasional hangover).

I enjoyed the book , though. It is an interesting mix of the personal, historical and geographical. It’s a glimpse into something few people experience. And while I don’t mean to offend Ihlenfeld if he is still working there, it is much better than Family Guy.

If you’re interested in this book, you may also be interested in


Ihlenfeld, Dave. Dog Days: A Year in the Oscar Mayer Wienermobile. New York: Sterling, 2011.

Monday, November 14, 2016

Lights Out by Ted Koppel

Much of the world, and America is particular, is heavily networked through a vast, distributed communication system of computers, cables, and transceivers. All this runs on electricity. Our major infrastructure is dependent on electrical power: water, sanitation, healthcare, communication and transportation. These systems, indeed even the systems that generate and distribute electricity are increasing controlled by networked computers.

This makes America extremely vulnerable to cyberattacks aimed at the electric system. If a major section of the power grid goes out, millions of people could be left without clean water, waste disposal and food. A well-orchestrated cyberattack could leave large parts of the country without power for as long as a year.

Journalist Ted Koppel explores this situation, and criticizes America’s state of unpreparedness and sometimes denial, in his book Lights Out. There are three major parts to his book.

First, he explores the vulnerability of the electrical system to cyberattack. I think he makes a fairly convincing case that the system is vulnerable and that some agents very likely already have the capacity to cause major damage to the system that could affect huge parts of the country.

Second, he looks into the state of our policies and preparedness. As you might expect for a nation of 50 co-sovereign governments, it is a patchwork. In addition, the major actors in preventing, planning for, and responding to catastrophes are focused on natural disasters or physical attacks by terrorists. These things shouldn’t be ignored, but the scale of a cyberattack on the electrical system could have a much larger scope in terms of the populations and territories affected.

Finally, he looks at how prepared the country is for the aftermath of such an attack. The answer is we are woefully unprepared. He looks into the prepper movement and the vast resources the Church of Jesus Christ of Latter Day Saints has put into readiness. He finds some models there, but no one has the resources to respond to such a massive disaster.

Of course, the issue is not simple. Preventing such an attack is difficult even if all the competing interests (utilities, federal agencies, local and state governments, privacy advocates, and many others) could agree on what to do, who should do it, and how far their authority should extend. It is all hugely expensive, especially preparing to respond to a massive outage, and it would take years to get ready.

Even so, Koppel clearly thinks we should acknowledge this vulnerability and start doing something about it. An imperfect plan, even if it is too little to late (it’s already too late because cyberattacks are already happening and major attacks could be launched with the press of a button), is better than no plan. He looks to the civil defense planning during World War II and the Cold War. Much of it was misguided or for show, but we learned valuable lessons that helped us make more effective responses and develop better policies.

Koppel writes as a journalist for a wide audience, and that was his intention. Readers do not need a background in engineering, utilities or security to understand the issues he brings up or their implications.

If you’re interested in this book, you may also be interested in


Koppel, Ted. Lights Out. New York: Crown, 2015.