40818... and all...
I am 54-yrs-young... and 28-yrs+ as a "self-supporting" aero engr [apr 79]. My "bio" as more info... for anyone curious enough to care..
The first true aero engineer I met was John Thorp. Brilliant; practical; hands-on; licensed professional engineer; experienced in aero-structural-mechanical-materials-electrical design and analysis; good draftsman; OK pilot; street drag-racer in his spare-time; all-around-auto-and-acft-mechanic; and capable buisnessman. What a guy: put a sheet of white paper in front of him, with a tasking order to design an aircraft, an acft Mod, or a telescoping crane, and he could do it under-budget and on-time... and it will be quite satisfactory. And THEN he would assist in the prototype fabrication, development and all aspecst of testing (ground and flight). In response to hard technical questions, JT could quickly run some "round-numbers" in his head and on a napkin; for an approximate answer... then, if needed, hit the slide-rule and calculator to firm-up a workable answer in a few days. I witnessed him do this several times for my Dad when he was modifying his homebuilt T-18 wings and fuel system for long-range flights (IE: integral wing-tanks)... in the early 1970's. He was the consumate "all-skills-engineer" of the 1940s-to-1980s. I have tended to model my careeer on his amazing example (too bad earning a living $$ has taken prescedence over being an independent engineer).
and then...
I've worked with some incredibly bright engineers [PHD, aerodynamics and FEA types] that had "0" [zero] practical sense of structures and mechanical "things", aging acft, flight operations, etc. What a nightmare... authority with NO practical value or experience. These folks couldn't chew bubble-gum and walk as straight-line... and had little credibility as an engineer (analysts are NOT engineers... unless they also walk-the-walk).
and...
I have worked with GI and civilian mechanics/technicians that span the spectrum from brand-new to old-gray-beards. The guys who wanted to do their work correctly and efficently, became masters at the trade... constantly learning and experiencing their craft... AND soaked-up experiences in other skill-fields. These guys and gals taught me hands-on skills in various fields/disciplines.. and critical, common-sense and out-of-the-box thinking processes. Many of the techs-mechs that appeared to be duds ("slow/lazy")... often became motivated when confronted with the broad/deep aspects of their career and mystical questions everyone askes themseles... such as "why-we-do-this, this-way" or "what are the implications of this", "is there a "best-way", etc... were addressed with hard facts... not smoke-and-mirror answers.
What I am saying, is that engineers (techs-mechs, etc) who attain and use a variety of knowledge, experience, hands-on skills, mechanical and technical "tools"... and are not put-off by hard-work and difficult choices [decision making] in the heat-of-action... are able to effectively solve complex-multi-faceted problems.
On the other-hand engineers with limited abilitys and skill-sets often approach complex problems with "no-clue" and fail by degrees. There is an old wise saying that expresses this thought: If the only tool You have is a hammer, then everying looks like a nail...
For insight into why some things work so well... and other things fail (in degrees), I suggest (2) small/obscure books for Your intellectual pleasure:
"Augustine's Laws" by Norman R. Augustine
"Systemantics: How Systems Work and Especially How They Fail" by John gall
After reading these You will be more concious of the reasons for broad skills, honest/critical thinking/criticism and "war-gaming" to look for pitfalls and quagmires in the work ahead.
Regards, Wil Taylor