To Engineer Is Human: The Role of Failure in Successful Design 
asked by vicky123 on October 30, 2006 6:28 PM
The moral of this book is that behind every great engineering success is a trail of often ignored (but frequently spectacular) engineering failures. Petroski covers many of the best known examples of well-intentioned but ultimately failed design in action -- the galloping Tacoma Narrows Bridge (which you've probably seen tossing cars willy-nilly in the famous black-and-white footage), the collapse of the Kansas City Hyatt Regency Hotel walkways -- and many lesser known but equally informative examples. The line of reasoning Petroski develops in this book were later formalized into his quasi-Darwinian model of technological evolution in The Evolution of Useful Things, but this book is arguably the more illuminating -- and defintely the more enjoyable -- of these two titles. Highly recommended.
Reviews
0%
0%
This book tries to answer the question of why the stuff built by engineers break, what a stupid quesion. Stuff breaks and stops working all the time, that's why we have quality control in factories. If someone thinks we can make something perfectly the first time and every time he must've been born yesterday or smoking. Think about the first plane built or the first car, the first train, the first computer, MP3 players that stops working in a week, umbrellas that flip in the wind... Maybe people don't die when these things break, maybe they do... but this has always been how technology develops---it improves over time.
The title of the book suggests that things built by God do not fail, wrong! Humans get sick, ozone layer gets holes, species go extinct, the Old Man of the Mountain falls flat on his face, and how about birth defects, the list goes on.
Not a well thought out book. And trust me when I say the writing style puts even a true nerd to sleep.
The title of the book suggests that things built by God do not fail, wrong! Humans get sick, ozone layer gets holes, species go extinct, the Old Man of the Mountain falls flat on his face, and how about birth defects, the list goes on.
Not a well thought out book. And trust me when I say the writing style puts even a true nerd to sleep.
reviewed by vladi on November 6, 2006 11:41 PM
0%
0%
I purchased this book at the Duke University bookstore, after the recommendation from a professor at another institution.
Petroski's prose is extremely dense and verbose. His style consists of run-on sentences which require several readings. Even if it is technically (grammatically) correct, it is extremely difficult to read. The subject matter is dry to begin with, however, Petroski does nothing to liven it. I am an engineer also, and am not threatened by the technical information (admittedly lifted from his students' term papers). I have chemical engineering textbooks that read like a novel. Hopefully the courses he teaches are clearer than this muddled prose.
Petroski is certainly an engineer. He has engineered an elegant method of making money from saps like us. I successfully engineered Petroski's book into a beverage coaster to help drown the sorrows of wasting $14 on this book.
Petroski's prose is extremely dense and verbose. His style consists of run-on sentences which require several readings. Even if it is technically (grammatically) correct, it is extremely difficult to read. The subject matter is dry to begin with, however, Petroski does nothing to liven it. I am an engineer also, and am not threatened by the technical information (admittedly lifted from his students' term papers). I have chemical engineering textbooks that read like a novel. Hopefully the courses he teaches are clearer than this muddled prose.
Petroski is certainly an engineer. He has engineered an elegant method of making money from saps like us. I successfully engineered Petroski's book into a beverage coaster to help drown the sorrows of wasting $14 on this book.
reviewed by waltersmith on November 16, 2006 9:12 PM
0%
0%
In this book, Petroski brings up a few good points. Engineering is human. Engineers, as oppose to what some think, are not perfect. They are not able to create a perfect design for the given problem. They create what they believe is the best solution for the given design specifications. They, along with others, test their solution, in theory. The majority of these solutions are created and succeed perfectly. Although most of these designs are successful, some are not.
It seems to be most of the failures of designs happen when it deals with something big, including the Kansas City Hyatt Regency Hotel walkways, which killed over 100 people, or the Tacoma Narrows Bridge. These failures become famous and the engineers are the first ones to be looked at.
Along with engineering success comes failure. This is a part of being human. Human engineering will always have its failures along with its successes. When engineers build something, they analyze it to determine if their solution is the best solution. Sometimes it takes a failure for the engineers to see their failures and to correct the problem. This book tries to explain this and does in most cases. In some of the cases, it leaves the reader wondering what else could have been done or what needs to be done in the future to prevent these failures.
It seems to be most of the failures of designs happen when it deals with something big, including the Kansas City Hyatt Regency Hotel walkways, which killed over 100 people, or the Tacoma Narrows Bridge. These failures become famous and the engineers are the first ones to be looked at.
Along with engineering success comes failure. This is a part of being human. Human engineering will always have its failures along with its successes. When engineers build something, they analyze it to determine if their solution is the best solution. Sometimes it takes a failure for the engineers to see their failures and to correct the problem. This book tries to explain this and does in most cases. In some of the cases, it leaves the reader wondering what else could have been done or what needs to be done in the future to prevent these failures.
reviewed by bigwinner on November 25, 2006 10:49 PM
0%
0%
The engineer's profession is notoriously fast-paced, and what is exciting today is ho-hum tomorrow. So it is with the failure cases outlined in this 1992 paperback. Not that these cases are dull - far from it! - but when the addendum at the end of this book was written the Challenger space shuttle had blown up and the disaster was just being figured out. Now we have seen the shuttle Columbia break up, as a result of NASA slowly forgetting the Challenger lessons.
With that problem so noted, I still strongly recommend this book as a great read if you want to find out what the business of failure analysis is. It is perfect for beginning engineers and for those who have an interest in the forensics of hardware like aircraft, bridges, and other structures.
With that problem so noted, I still strongly recommend this book as a great read if you want to find out what the business of failure analysis is. It is perfect for beginning engineers and for those who have an interest in the forensics of hardware like aircraft, bridges, and other structures.
reviewed by caramel on November 26, 2006 2:11 PM
0%
0%
A little wordy. Suggsted for serious work not for casual reader.
reviewed by casurf on November 28, 2006 7:33 PM