Dr. Petroski--absolutely fascinating article. I love these stories that give background and weave into the narrative personal history regarding the engineer(s) doing the work. We sometimes forget that many many great engineering designs were accomplished with slide rules, pencils and erasers. (Big erasers at that.) Really demonstrates how far we have progressed with technology. I wonder where we will be fifty years from now. Again, many thanks.
The comment about secondary required designs brings out the old comment "Nothing is ever simple". The truth is that usually an over-all design does require a lot of little designs, such as nuts and bolts. The good news is thgat we don't need to design those parts new each time.
Design does beget design. In the article, the design of the demo was a result of the design of the bridge. That is the circle of life of engineering. If you design an end item, there are many other designs that are necessary to make your assembly a reality. If the component requires plastic parts, someone has to design the molds for the part. Someone else handles the design of the molding mahcine to run the molds. This goes on up and down the chain keeping engineers in business.
An interesting title, although my experience is that designs build on designs. It is often easier to imagine an improvement of some kind when looking at a design then when looking at a blank sheet. Even an unworkable dsign can serve as a basis for ides to produce a much better design. At least that is often what I see. Of course, sometimes we can only guess about what the main goal of a design was. Some designs seek to minimize the required accuracy of components, others strive for the maximum robustness, and it is obvious that many designs are optimized for minimum initial cost, with little attention given to other variables.
So every design can serve as a basis for additional designs, optimized for some particular variable parameter.
Sorry, Mr. P, I had no idea there was any such limitation, it seems I see photo's here quite regularly. Editor?
Bob from Maine, I'm quite proud of my ability to describe things accurately, but like most engineers regardless their artistic ability, I am always sketching stuff during discussions. One wouldn't commit schematics or drawings to a written description. Imaginations are way too variable to assure our minds are on the same page.
I'd seen this fantastic photo some time ago too, (Perhaps in Mr. P's book) and although it all sounded familiar, I still didn't put it together.
This article may not be illustrated, but "Engineers of Dreams" is, and I remember the image shown below is in that book. I've kept it on my shelf waiting for my son to be old enough to understand and appreciate it as he heads towards an engineering career.
Ken, You are absolutely correct. A picture is worth a lot of words, but it was my understanding that my column was not to be illustrated. Thanks to Mr. Palmer for inserting the classic photo into his comment. HP
Using words to let us paint our own mental picture is to me the essence of teaching. Teach us to read and imagine, then present a problem and describe a solution and let our minds create the picture and fill in the details. I read the article and had a pretty good concept of what was being described, when I saw the photo, it was obvious what had been described and the details clicked immediately into place. I think those of us who learned to read before there was television may be luckier than our children who had all the solutions presented visually before they developed the ability to imagine. I always enjoy your articles Professor Petroski.
Festo's BionicKangaroo combines pneumatic and electrical drive technology, plus very precise controls and condition monitoring. Like a real kangaroo, the BionicKangaroo robot harvests the kinetic energy of each takeoff and immediately uses it to power the next jump.
Design News and Digi-Key presents: Creating & Testing Your First RTOS Application Using MQX, a crash course that will look at defining a project, selecting a target processor, blocking code, defining tasks, completing code, and debugging.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.