Most Helpful Customer Reviews
31 of 31 people found the following review helpful:
4.0 out of 5 stars
An Interesting Topic with Repetitive Examples, June 11, 2000
To Engineer is Human is a surprisingly relevant book, despite being 15 years old now. Some of the examples may tax the memories of younger engineers and engineering students, but that's exactly the point of this book, to emphasize the nature of engineering: improving what has already been done in the past.
I, too, found the repetitive references to a limited number of examples tiring; I suspect this was done because Petroski had prior knowledge of these case studies and wished to minimize his research by drawing on what he knew about before writing. As an amateur historian of technology, I was also disappointed that few earlier historical examples were treated in any depth, the Crystal Palace being a notable exception.
The book is an easy read. Henry Petroski's prose is easy to grasp and flows well, holding the reader's interest, despite the repetition.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
23 of 23 people found the following review helpful:
4.0 out of 5 stars
Accessible even to my grandmother, April 20, 2001
In this enlightening book, Petroski, who is professor of civil engineering, has succeeded admirably in conveying what engineering is and what engineers do in a manner that is accessible even to my grandmother, i.e., the general public. His presentation, although somewhat repetitive, is clear and sprinkled judiciously with humor. Moreover, it is illustrated with familiar analogies, and also numerous mechanical and civil engineering examples including everyday objects such as paper clips, toys and knives. To engineer is to design, `making something that has not existed before'. Petroski provides insights into the design process (which involves computers extensively nowadays) and its limitations, and also the means employed by engineers to prevent failures in their designs. He emphasizes, however, that it is not possible to anticipate all possible ways a design can fail and thus failures inevitably occur because engineers are, after all, humans. Numerous examples of catastrophic structural failures throughout history are presented and discussed. All involved the tragic loss of lives (for instance, the collapse of two crowded suspended walkways onto the crowded floor of the Kansas City Hyatt Regency hotel in 1981) except the collapse of the Tacoma Narrows bridge in Washington State in 1940. Petroksi also discusses the failure analysis or forensic engineering that is performed in the wake of a catastrophic design failure to understand how and why the failure occurred. He argues convincingly throughout the book that understanding such design failures can advance engineering more than successes. Design failures, like other failures in life, should be embraced, rather than denied or ignored, and learned from. Great engineers, and great people in general, are the ones who heed George Santayana's famous dictum: `Those who cannot remember the past are condemned to repeat it.'
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
31 of 33 people found the following review helpful:
4.0 out of 5 stars
Why can't a car be built that is totally crash-proof?, February 14, 2001
The answer is well explained in this book. By the time you built such a car, it might be so heavy it couldn't move! The real interest in this book are the analyses of various disasters that should have been planned for, but weren't. The most terrible engineering disaster (and the reason I bought this book) was the collapse of the sky walkway in a hotel in Kansas City in the 1980's. I was just returning from KC when I heard the horrific news on the radio. The skyway collapsed during a dance, killing hundreds and injuring more in a dreadful disaster. I was very upset by this terrible event. Why did this happen? The explanation in "To Engineer Is Human" is really brilliant; the walkway was designed "properly" with a bolt that went through the beam supporting it. But it could not be built as designed because the bolt couldn't be installed in the vertical support. Instead, the builders split the vertical support into two parts in order to install two bolts, and each part was then able to move independently, causing a shear force that eventually led to the disaster. A brilliant analysis and one that showed that despite correct design, the plan must be able to be implemented to work--or else the execution of the plan may doomed to disastrous failure. That lesson is really important when you are engineering anything, even software. You may specify an important feature, but if the R&D department cannot implement the plan, the product may fail to meet its goals, even be defective. The book is a bit "thin"--I wanted more and wished it were longer and had more detail, but I will say it makes its point and memorably so. After reading it, your eyes will be opened to how things are designed, how things fail and how engineering affects our lives.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
|
