To Engineer Is Human: The Role of Failure in Successful Design

I am not really sure how I came across this book. I think it was by following relevant links on Amazon. Anyway I bought this as well as The Evolution of Useful Things at the same time. I found this a very insightful reading in light of my occupation as a software engineer. Several of my coworkers recently had an email conversation regarding the quailty of software engineered products vs. "real" engineer's and their feats of construction, bridges, airplanes and buildings all things that Petroski covers in details.

Some additional thoughts on how structural engineering is different from Enterprise Application Software Engineering:

1. --In general software is unlimited, where as Structural Engineering has natural laws. Higher level Patterns are pretty constant, where as within the created construct of software they are reinvited (Object Patterns, EJB Patterns)
2. --structures have the added requirement of no death, where as Enterprise Software only has revenue associated with it, not as powerful a motivator as death.
3. --software is interactive with behavior, where as a bridge is a bridge

http://www.niffgurd.com/mark/books/2002.html#eng

Why do buildings and bridges suddenly collapse, or why do airplanes fall out of the sky ? Even though since the start of the industrial revolution the relative number of disastrous accidents has gone down, it is still a daily event.
Some great examples are given (most prominently the walkway of a Houston hotel that collapsed during the opening ceremony) with pictures and detailed analysis. Great stuff even for non civil-engineers since with some imagination you may learn some more general design lessons.
The editorial side of the book is less impressing, most facts and interpretations are repeated 3 or 4 times throughout the book (excluding the introduction and back flap) so I never got further than 3 quarters into it, preventing myself from another deja vu.
In any way, a veryimportant and useful read.

I found the book absolutely fascinating, especially since I am a mechanical engineer by education and experience. To Engineer is Human covers some of the greatest engineering disasters in modern times such as the Tacoma Narrows bridge collapse, the Kansas City Hyatt Regency Walkways collapse and the Space Shuttle Challenger disaster.

Henry Petroski explains the engineering disaster in great detail and then explores the causes and effects. He then explores how (if possible) the disaster could have been avoided.

Well written and understandable this book is a masterpiece. One of the primary things that all good engineers do is to contemplate the "lessons learned" after any significant endeavor...whether it has good or bad results. As the old saying goes: Those who don't learn from history are doomed to repeat it!

Engineers as well as anyone else who has an interest in engineering marvels and what can go wrong will find this book entertaining, informative and well researched.

The Re-Discovery of Common Sense: A Guide to: The Lost Art of Critical Thinking

Here it is. I purchased this for my Dad, 79 years young. Finding anything for him, that he hasn't seen, heard or done is very difficult. Imagine my surprise when he sent me a note stating this was the BEST gift he'd received in a long time! I also bought him "the Evolution of Useful Things"... same message! Both are super-duper gifts!

This little gem is an analysis of engineering failures, and the learning that occurs due to these failures. While he is himself a professor of engineering, Petroski uses language comprehensible to the layman making this book accessible to almost anyone. During the course of the book he argues that engineering is part art and part science, and that as a discipline engineers focus on building safe, affordable, and reliable things (from paper clips to airliners) to meet a set of requirements. He goes on to elaborate that, being human, engineers make errors and sometimes spectacular failures ensue. The key, he argues, is that once errors are exposed, engineers can glean knowledge from those problems to improve future designs.

He uses accessible examples that most people can readily relate to, from researching failure modes on one of his son's toys (the components used most frequently failed first, just like a frequently used light bulb burns out more quickly due to metal fatigue and subsequent cracking), to the deadly collapse of the Kansas City Hyatt Regency Hotel walkways, which killed over 100 people. He also discusses easy to comprehend failures (suspension bridges in strong wind), and more intricate interactions, such as was revealed in the Chicago DC-10 accident. Throughout, he retains an aura of good humor and approachability, which makes this book far more readable than most books in this field.

My only complaint about the book is not even the fault of Mr. Petroski at all: the font in the book is very small, and combined with small borders, the book is a bit tough to physically read. Small matter, though, as once you start the book, you will not want to put it down. Well done.