What's also amazing is how what was once almost unthinkable--rendevous in Earth orbit, Moon orbit, and even Mars Orbit--now has become routine, to the point where the public is jaded and blase about it.
It's another example of how when you perform these "miracles", you end up making your work seem simple and trivial, and thus it is not appreciated. No good deed goes unpunished, as they say, and beware the law of unintended consequences of your accomplishments.
When I hear the term "team player" being thrown about, I've long since come to think "milquetoast," worker bee, company man. In other words, pejorative terms.
Of course, anyone who does not "go along to play along" had better be right, at least most of the time. The problem is self-regulating. Anyone who has a mind and speaks it, if he isn't right overwhelmingly often, will not remain employed very long.
Thanks for the link. I now know more about Houbolt.
Unless today's space experts learn to emulate Houbolt's vision, courage, and soft-spoken stubbornness, the grandiose "Vision for Space Exploration" plans for resuming human flight beyond low Earth orbit may fail to be realized.
The truly sad thing is that most organizations (eveyone I have seen or heard about) don't care if your right these days. Sure being wrong will get you in trouble because most failures need a scape goat.
Being correct is typically the worst option if you try and push your ideas against resistance. You can try going over your bosses head or even pushing your idea in a public forum having your idea critisized by your boss as not preferred. That is a short road to the end of your job these days. It does not matter if you are right.
The path to success is to suggest the correct awnser and if those in charge dont claim credit for your ideas then the idea dies a quite death. That is a big reason why North American companies are such lame ineffective places to work now a days.
Hats off to NASA for being so close to a meritocracy that you could go 6 levels above you on the org chart and keep your job....and have the company accept your solution. Not much of that going on around here any more.
Of course, it helps if there is a ladder or org chart in the first place--too many companies are in such constant internal turmoil/churn that you can't figure out who the level above actually is, iwth job titles/functions that obscure rather than define--it's especially the case for the one(s) above the one right above you.
I'd say it depends on the boss. Those that have confidence in themselves will help you push ideas they think will work up the chain, even carry it for you. The insecure ones will eather shoort your ideas down because they see you as a threat of will claim the idea as thier own. It's called politics.
You can try going over your bosses head or even pushing your idea in a public forum having your idea critisized by your boss as not preferred. That is a short road to the end of your job these days. It does not matter if you are right.
It is refreshing to read about John Houbolt, thank you. Without the aid of computers that we take for granted (and carry one in our pockets that is much more powerful that Apollo's on-board ones!), he solved tough problems with hard-core engineering knowledge, analysis and hand calculations. It is a tragedy that we are losing the generation of these real engineers with nary a few to replace them.
I'm sure there are engineers today who are just as willing to risk their careers for a solution they think is right. (We call them startups.) I would also like to compliment his choice of tie the in photograph on first page.
There are worse things than getting fired, if that's the big fear here, Martin. John Houbolt was a public servant doing his job. Maybe not doing your job is worst than getting fired. It depends on your personal integrity and what you are willing to live with.
Along with congrats for his mind and bravery and condolences for John Houbolt's passing, we can take away some engineering thoughts, too.
A big problem is a lot of little problems.
Each solution has its own needs and its dunnage - e.g. photos need to be as clear as possible, but they don't need colloidal plates and wet baths, or developing fluids, or sheet film or wires or even lenses.
Don't own more of a solution than you need to.
Use the engine, burn the crates, eat the freight horses.
The lander module only had to support itself and the recovery module for One Landing! Look at how much simpler both up- and down stream tasks become.
My father worked for a compan ycalled Jan Hardware in the 1960s. His company made the large knobs all over the LEM instrument panels. They had a slip-clutch mechanism so the know would keep turning when it reached the end of its travel. It solved the problem of when astronauts would strip the knob's inside whiel wearing heavy gloves.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.