The com­plete title of this amazing book is To Engineer is Human, The Role of Failure in Suc­cessful Design. I’m pretty sure all of you struc­tural engi­neers, or any other type of engi­neers for that matter, have already read this Pet­roski title, but for everyone who is not yet acquainted with Pro­fessor Pet­roski – espe­cially all you writers – this is a must read. There’s one other group of people out there who also might be inter­ested: anyone who’d rather not fly, cross long sus­pension bridges or live too close to a dam.

Henry Pet­roski is a pro­fessor of engi­neering and history at Duke Uni­versity. He is also one very ter­rific writer who has a lot to say in this book about design failure in the world of suc­cessful struc­tural engi­neering. To Engineer is Human is a book for all of us who’d like to know a little more about those bridges that col­lapsed, planes that fell from the sky, buildings that needed shoring up or any of the other mys­teries of failure that haunt us all. Maybe you’ve always won­dered why you failed that one exam you thought you had nailed; what the heck, Pet­roski may even give you some insight as to where to look for the reasons your mar­riage failed or even how to take a second look at that poem that refuses to stay put on the page.

Petroski’s opening clearly states what he and this book are about: “I believe that the concept of failure – mechanical and struc­tural failure in the context of this dis­cussion – is central to under­standing engi­neering, for engi­neering design has as its first and foremost objective the obvi­ation of failure.” Obvi­ation is a big word in this book and one which I can now use with great aplomb.

Petroski’s use of the history of great struc­tural designs, the pyramids, Gothic cathe­drals, famous bridges, is just one of the ways he takes the reader into an up close and per­sonal encounter with struc­tural engi­neering. Where was he when I needed him in high school to explain the rela­tionship between theory, hypothesis and fact? The clarity of his writing and the no-​​nonsense way the book is put together (all right, designed) makes it won­der­fully worth the read. The copy I read for this review was the 1992 updated edition (orig­i­nally pub­lished in 1985); the reader travels from the pre-​​pyramids of 2700 B.C. to early 1990s com­puter design, including occa­sional inter­ludes into the lives and works of some rel­evant and fas­ci­nating lit­erary figures.

The book covers the struc­tures them­selves and the ele­ments of their building mate­rials, and, toward the end, takes a very eye-​​opening look at the way in which struc­tural failures are inves­ti­gated by all the bodies politic, eco­nomic, and design, both before and after the acci­dents. Petroski’s take on the use of com­puters for design is a bit unnerving: “And as more complex struc­tures are designed because it is believed that the com­puter can do what man cannot, then there is indeed an increased like­lihood that struc­tures will fail, for the further we stray from expe­rience the less likely we are to think of all the right ques­tions [my emphasis].”

To Engineer is Human is science, art and always enlight­ening. Who else but Pet­roski could include the pyramids and a nar­rative poem by Oliver Wendell Holmes; the history of the first steel-​​reinforced con­crete and a novel by Nevil Shute that would serve notice to an industry on the necessity of vig­ilant main­te­nance? This was Petroski’s first book and those that fol­lowed con­tinue to capture the imag­i­nation of engi­neers and laypeople alike. Join the crowd; you’re in good company.

Buy To Engineer Is Human: The Role of Failure in Suc­cessful Design locally or look online at Amazon​.com, Powell’s Books, through an IndieBound book­store.  Thanks.

 

Leave a Reply