The narrower the technical skills, the faster you need to replace the labor. Today's AI experts will be tomorrow's geezers w/ outdated tech skills. And by tomorrow, I mean 3 years or so. |
The best evidence that you're going to stay current is that you've already been able to update your skills. Obviously at some point age comes for us all, but someone who is already left behind isn't going to get less left behind. |
If you're interviewing the phds, they are not the old employed phds prev mentioned. The new stem hires do so much worse. They do everything thing in jupyter. Literally their "work" is a huge useless notebook. The old phds know how to archtect code, do cron and nohup. New hires don't know much of linux. |
...says the young inexperienced new grad who is fearing for his job at MITRE. |
Not everything at Mitre was software in the past. They ought to have experts in areas like RF and EW, although maybe Mitre dropped technical work when they started their big IT focus. Even SDRs require substantial RF design knowledge - modulation, coding, resilience, LPx. |
I have both worked with and interviewed older PhDs. I have no older vs. younger or PhD vs. not PhD fight. From all of these, some are terrible and some are great, but I'm not assuming any degree of competence or ability to learn based on a degree. |
Smart. |
It was pulled….. https://www.rand.org/pubs/research_reports/RRA4107-1.html |
I thought you were the 'old geezers' poster. It gave me a chuckle reading that he thinks younger engineers 'who can actually help government counterparts', but in truth they just don't know enough to know what they don't know. |
Hire young people who think like consultants and not engineers. Consultants get a bad rap, but they can usually can take action and produce results instead of govies who just check their PTO balance 8 hours a day. |
And I've worked with a lot of narrowly focused software engineers who only care about clean, modular, commented code, that has to go through rigorous MRs where you nit pick on every little thing. There's a time and a place for each. PhDs (painting with a broad stroke) are great at solving the hard technical problems. They won't make production software. But that's not what they're paid to do. <--- not a PhD |
Different parts of Mitre do. I've worked with a lot of RF SMEs. |
I'm not talking about production software, I'm talking about being able to turn in code that actually ran and was usable. That was their job and they were failing to do it, or it was the job they were applying for and not getting. Again, not all PhDs, but I was explaining why having a PhD is not a signal of willingness to learn or ability to do it. |
Are you a CNA bootlicker? Current IPR VP making over $250k/year, with high bonuses, can't market IPR work as a former FED even after your restrictions have expired? The FFRDC portion is safe/sound for now as the Navy/Marine Corps requested changes at the FFRDC. IPR still has a high overhead rate. |
AND, more importantly, it's listed on that link as cost with no fee. Losing that fee is huge. |