The details, oh, the details. Why is it that we do not check them more carefully? For they can send innocent readers into the bowels of libraries, where madmen mug books, and they can send innocent citizens to their deaths in cracked airplanes and on shaky skywalks.
I’ll admit some bias in picking up this book; I’m entering college next year as an intended dual major in engineering and art, and a book subtitled “The Role of Failure in Successful Design” was just too good to pass up. I read To Engineer is Human with the intention of gleaning a few possibly life-saving lessons about the queer field I’m entering – and although Petroski’s pedigree is in civil engineering, many of his points are important across the board.
That being said, Petroski’s book may not be as suitable for the layman as he originally desired. There were several parts where I found myself saying, “I’d be lost if it weren’t for the fact that I know about all this stuff already.” The anecdotes are a bit hit-or-miss, the best one probably being the story of the Crystal Palace.
Although the effect is overall limited, the book falls into that all-too-familiar rut where the science outweighs the human effect on the reader. Petroski definitely relates his content all back eventually, but getting up to there is daunting.
(It doesn’t help that there’s one chapter basically ranting about how errors in computer design are going to be the bogeyman of the twenty-first century – like, why not call in some civil engineering experts to help design the system? Serious bro points lost with this Linux geek.)
A good and informative read for aspiring engineers (and maybe practising ones). Maybe a bit too intense for the average Joe.
But! For those of you who are in the civil engineering purview of interest, check out the related content links.