| ||||||||||||||||||
![]() Trade In this Item for up to £0.25
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in To Engineer is Human: The Role of Failure in Successful Design for an Amazon.co.uk gift card of up to £0.25, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Product details
|
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
This book documents how successful engineering is a process of predicting and preventing failure. Several chapters offer a variety of viewpoints on the philosophy of design: engineering as hypothesis (this building will stand up) which is tested analytically or empirically; design as revision (if we change this bit it will stand up); success as foreseeing failure etc.
There are several good angles here, particularly where Petroski likens engineering design to the way in which children learn. For non-engineers, there is also useful material on factors of safety, failure by cracking and other basics.
Petroski's use of language is excellent, but as an engineer, I do find a lot of the book disappointing. Non-engineers might come away thinking they know why Tacoma Narrows collapsed, or what fatigue cracking is, but the technical reasons are at best alluded to, never properly explained. Petroski's paper-clip example for fatigue cracking is particularly poor, as it mixes in two generally unrelated issues (brittle failure and plastic strain hardening; although ultimate failure is indeed due to fatigue cracking). For technical matters, "Why Buildings Fall Down" by Matthys Levy and Mario Salvadori is far superior, and much better illustrated with simple and easy-to-follow diagrams.
Where Petroski succeeds is in the human processes of design engineering, but even here he is somewhat weak. He's good on the philosophy but not the reality - you couldn't read this and get any grasp on how a design engineer actually spends their day, for example.
Worth reading, but let down by its fear of the technicalities.
The second half, for me, made it worth wading through all this; although the author still did not always follow through the thoughts that he fired off. The section on the crystal palace was fascinating, as was the story of the 50th anniversary of the Golden Gate bridge in the Afterword to the Vintage edition
For me, the whole book was worth the single sentence "designed objects change the future into which they will age"; in other words new technology leads to ...new ways of doing things which leads to ...new possibilities of failure which ...were not covered in the design because people didn't do things that way then.
Not a brilliant book, and some pretty basic gaffes which are difficult to understand - but worth reading as a whole.
Brad Flack John Deere Harvester HX25187@Deere.com
|