To Forgive Design Download ê 104

Henry Petroski ´ 4 Download

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 lea. Reading this made me appreciate that things don t fail often than they do A bridge or space shuttle or parking garage or de icing boot on an airplane is a complex system it may have been built with redundant safety tolerances but one shoddy material or one sub contractor who didn t pour the concrete properly or an addition that added different stresses or an increase in use or an environmental factor heatcoldsalt water corrosion or a new way of using it or some repairs made with a new materialand it breaks Petroski examines how engineers learn from the process of breaks designing things that avoid fatalities and damage through managed failures testing and designing safety tolerances attempting to have designs carried out in transparent and safe construction practices the national characters of Briti

Summary ☆ PDF, DOC, TXT or eBook ´ Henry Petroski

To Forgive Design

He Minneapolis bridge collapse and the toppling of a massive Shanghai apartment building in to Boston’s prolonged Big Dig and the 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 contradictionsFailure. This is an engaging although lengthy read I admit I resorted to skimming through much of the book since I got it from the library and only have so much time However the central premise of the book is clearly true studying failure should be a never ending activity for engineers and those involved in management of engineering projects A few lines present the premise very clearly One might as well just be the summary of the lesson we should take from the book It is imperative that the realistic prospect of failure be kept in the forefront of every engineer s mind Another in reflecting on the hundreds of years of books on what we today call engineering or design captures the historical view as well One thing that especially impressed me was that seeming no matter when a book on design was published it di

Summary To Forgive Design

When planes crash bridges collapse and automobile gas tanks explode we are uick to blame poor design But Henry Petroski says we must look beyond design for causes and corrections To Forgive Kindle 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 occurIn To Forgive Design he surveys some of the most infamous failures of our time from t. This book is a combination memoir and history of design failures From the patterns developed by the relationship between failures and the striving for economical design the author draws conclusions regarding the dangers that can emerge from complexity and the subseuent passage of old designs on to new generations of designers who have forgotten old lessons Unexpected and unintended failures are obviously bad but once they occur the lessons learned are very valuable The whole process of understanding why the failure occurred as well as why the cause was missed in the design process are necessary for progress to be made Sometimes the design is adeuate but the construction process or the manufacturing of the material failed to meet the design intent Other times improper maintenance and corrosive environ


10 thoughts on “To Forgive Design

  1. says:

    This book is a combination memoir and history of design failures From the patterns developed by the relationship between failures an

  2. says:

    I got this from the library with

  3. says:

    And I thought I understood failure Boy how I understood failure I thought I had mastered it but evidently there is so much to experience It must be difficult to edit a book on a technical subject written by an expert Perhaps the editor doesn't want to intervene forcefully at the risk of removing technical deta

  4. says:

    This is an engaging although lengthy read I admit I resorted to skimming through much of the book since I got it from the library and only have so much time However the central premise of the book is clearly true studying failure should be a never ending activity for engineers and those involved in management o

  5. says:

    The case studies presented have been discussed elsewhere in comparable detail with similar conclusions Aside from the author's tales of his own past there was little in the way of original insight

  6. says:

    While this book was written for engineers I who am NOT an engineer still found it thought provoking entertaining and informative Petro

  7. says:

    I like it because it is a non fiction book I appreciate the thorough explanations about metal fatigue testing strength of building materials and

  8. says:

    Reading this made me appreciate that things don't fail often than they do A bridge or space shuttle or parking g

  9. says:

    Numerous good accounts of why we need to break the taboo that holds that failure has nothing to teach us other than not to repeat that particular mistake I liked it for the insights on the intersections of technology socio economic context and learningprogress On another level I saw in it some good cross over applications to the management of technology support services which is my line of workview spoilerBri

  10. says:

    Petroski starts out strong with numerous descriptions in rapid succession of structural concrete related failures highligh

Leave a Reply

Your email address will not be published. Required fields are marked *