To Engineer Is Human

The Role of Failure in Successful Design

De: Henry Petroski

Narrado por: Matthew Boston

How did a simple design error cause one of the great disasters of the 1980s - the collapse of the walkways at the Kansas City Hyatt Regency Hotel? What made the graceful and innovative Tacoma Narrows Bridge twist apart in a mild wind in 1940?

How did an oversized waterlily inspire the magnificent Crystal Palace, the crowning achievement of Victorian architecture and engineering? These are some of the failures and successes that Henry Petroski, author of the acclaimed The Pencil, examines in this engaging, wonderfully literate book.

More than a series of fascinating case studies, To Engineer Is Human is a work that looks at our deepest notions of progress and perfection, tracing the fine connection between the quantifiable realm of science and the chaotic realities of everyday life.

©1992 Henry Petroski (P)2018 Tantor

A very thought provoking analysis

The title says it all. It's a an analysis of the human element of engineering. It's detailed and thorough but, not pendantic.I found it very thought provoking. The narration is good and is what I imagine the author intended as far as tone.

No "Monday morning QB" When Lives Are At Stake

I really wanted to like this book,but was immediately turned off when the author was describing the backlash from the engineering community after the disaster. There are some professions where you are dealing with the health and safety of the public and better have looked over those plans, materials, and construction techniques backward, forward and in a loop de loop to make sure the construct is safe. While there is always a chance of error where human activity is concerned, taking the TIME and RESPONSIBILITY to make that error as narrow as possible is, i.e., won't result in the loss of human life is the way to go.

Very interesting

Sometimes dry and sometimes outdated, but it did introduce many interesting outlooks on engineering that are still relevant today.

great book

It's a great book on the theory behind engineering failure's and their affects on future design.

What were they thinking or did they?

As an engineer with advanced degrees and 45 years of experience, this book did not tell me anything new. However, it was an interesting presentation on design failures more geared to the layman.

Very useful insights

Shows how successes become failures and failure may become successes. A book I feel I will listen to for years to come.

Not worth it

Dated 1985 or so, and horrible reading . And beat each episode to death.

Only listened because I was bored .

A great listen for the aspiring engineer

I really enjoyed it. The content and the lessons were were arranged and balanced to provide a valuable perspective on engineering and technology in general. A wonderful reminder of the importance of detail to the entirety of any design. A positive yet sober response to the issue of development and progress.

Not Sure Who The Intended Audience Is?

This felt like three books in one. It does have chapters detailing excellent examples of historical triumphs and tragedies, but most of the book was spent either describing engineering to non-engineers, or discussing common pitfalls with fellow engineers. In particular, it alternates jarringly between reminding engineers how difficult and complex their profession is, and assuring non-engineers that engineers have everything under control. I'd advise skipping chapters and fast-forwarding liberally.

interesting case studies, but diluted

The case studies are quite interesting, but these are diluted with lots of other less relevant material.