- Gebundene Ausgabe
- Verlag: St Martins Pr; Auflage: 1 (Juni 1985)
- Sprache: Englisch
- ISBN-10: 0312806809
- ISBN-13: 978-0312806804
- Größe und/oder Gewicht: 1,9 x 15,2 x 21,6 cm
- Durchschnittliche Kundenbewertung: 10 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 263.811 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
To Engineer Is Human: The Role of Failure in Successful Design (Englisch) Gebundene Ausgabe – Juni 1985
Kunden, die diesen Artikel gekauft haben, kauften auch
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
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. -- Dieser Text bezieht sich auf eine andere Ausgabe: Taschenbuch.
"Reading Petroski's fine book is not only a delight, it is a necessity." --Houston Chronicle
"Serious, amusing, probing, sometimes frightening, and always literate." --Los Angeles Times -- Dieser Text bezieht sich auf eine andere Ausgabe: Taschenbuch.
I agree with previously posted reviews here that this work is repetative and covers engineering failures at a very high level. However, I believe that this is an important work for those that do any type of complex design or work with designs.
I am not an engineer -- I'm an information systems professional who believes that professionals should be able to review failures, even those of other professions, to better address risk in future projects. The author does a great job of introducing this concept in this book's preface:
"...I believe that an understanding and appreciation of engineers and engineering can be gotten without an engineering or technical education.... I believe that the concept of failure - mechanical and structural failure in the context of this discussion - is central to unerstanding engineering, for engineering design has as its first and foremost objective the obviation of failure. Thus the colossal disasters that do occur are ultimately failures of design, but the lessons learned form those disasters can do more to advance engineering knowledge than all the successful machines and structures in the world."
Take the word engineering out of the above quote and insert any profession there and the quote still works.
I found particularly erie the background on the Comet, the first commercial jet aircraft. In the the chapter on Forensic Engineering, Petroski tells of a early Nevil Shute novel, _No Highway_, in which Shute tells a very, very similar _fictional_ story about a failed commercail aircraft called the Reindeer. I did not know that Shute was an aero engineer working for de Haviland at the same time as the Comet design.Lesen Sie weiter... ›
To his credit, Mr. Petroski's writing style is approachable by non-engineers, a feat that is probably worth at least one star all by itself. But it is a shortcoming that considerable detail has been sacrificed, perhaps in an effort to make the text palatable to a non-technical audience. The resulting text glosses over mechanical reasons for the design flaws under consideration. In some instances, such details are probably not all that important. To be fair, lengthy technical explanations about collapsed bridges, broken ships or fractured colums might render this book even less marketable than it is (at present, it hovers below 14,000th on Amazon's sales ranking). In those cases, the omission simply makes the account less satisifying to the overly curious reader.
But that is not always the case, and some examples would have benefitted from more detailed explanations for two reasons. First, since the book is about learning from mistakes, it would have been valuable to understand the mistake itself. That knowledge would help the reader appreciate how subsequent engineers evaluated a problem, identifed its cause and avoided repeating the mistake in analogous situations. Second, and more troubling, some omissions are confusing. For instance, the Challenger disaster is compared to the aforementioned Greek column problem.Lesen Sie weiter... ›
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.
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
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.
Die neuesten Kundenrezensionen
A must have for the design engineers. There is almost no other book, which can explain so many important aspects of engineering design, with clear yet casual and simple style. Lesen Sie weiter...Vor 7 Monaten von Mubeen veröffentlicht
... nur etwas duenn im Inhalt. Ich meine, die Beispiele und die Erklaerungen daran anlehnend sind ganz gut auch fuer den Laien verstaendlich, nur eben hab' ich, als einer der seit... Lesen Sie weiter...Vor 18 Monaten von Anonymous Coward veröffentlicht
Can you help me connect with the makers of the Video by the same title......To Engineer is Human? The company is Films Inc. Lesen Sie weiter...Am 19. Juli 1999 veröffentlicht
This book left me a little dissapointed, Petroski had a full tank of gas and only drove around the block. Lesen Sie weiter...Am 16. November 1998 veröffentlicht