To forgive design
understanding failure
Our rough guess is there are 105,500 words in this book.
At a pace averaging 250 words per minute, this book will take 7 hours and 2 minutes to read. With a half hour per day, this will take 14 days to read.
How long will it take you?
This book will take an estimated to read at a reading speed averaging words per minute. With 30 minutes per day, this will take to read.
Enter your reading speedYou can take one of our WPM reading speed tests to find your reading speed.
Create a free account to track your reading progress, build your reading list, and set reading goals.
Author
Publication
2012 - Belknap Press of Harvard University Press, Cambridge, Mass, Massachusetts
Language
English
Word Count
105,500 words, Guess
Page Count
422 pages
Physical Format
Hardcover
Identifiers
- Open LibraryOL25079156M
- ISBN-139780674065840
- ISBN-100674065840
- OCLC Control Number758244510
- OCLC Control Numbertoforgivedesignu0000petr
and 1 more
- Library of Congress Control Number2011044194
Classifications
- DDC620/.00452
- LCCTA169.5 .P48 2012
Description
When planes crash, bridges collapse, and automobile gas tanks explode, we are quick to blame poor design. But Henry Petroski says we must look beyond design for causes and corrections. Known for his masterly explanations of engineering successes and failures, Petroski here takes his analysis a step further, to consider the larger context in which accidents occur. In To Forgive Design he surveys some of the most infamous failures of our time, from the 2007 Minneapolis bridge collapse and the toppling of a massive Shanghai apartment building in 2009 to Boston's prolonged Big Dig and the 2010 Gulf oil spill. These avoidable disasters reveal the interdependency of people and machines within systems whose complex behavior was undreamt of by their designers, until it was too late. Petroski shows that even the simplest technology is embedded in cultural and socioeconomic constraints, complications, and contradictions. Failure to imagine the possibility of failure is the most profound mistake engineers can make. Software developers realized this early on and looked outside their young field, to structural engineering, as they sought a historical perspective to help them identify their own potential mistakes. By explaining the interconnectedness of technology and culture and the dangers that can emerge from complexity, Petroski demonstrates that we would all do well to follow their lead. - Publisher.
Description
Argues that failures in structural engineering are not necessarily due to the physical design of the structures, but instead a misunderstanding of how cultural and socioeconomic constraints would affect the structures.
Reader Reviews
No reviews yet for this book.
Be the first to share your thoughts!