Oddly enough, I was fired from that gig for witnessing a senior manager repeatedly mute the conference call to make racist remarks about overseas staff.
This sounds like the perfect opportunity to have your phone in your shirt pocket such that the camera just barely peeks above the cuff of that pocket. As long as you are in a one-party-consent region (most states, all of Canada), you can have some pretty juicy stuff that HR can make “go away” with a golden parachute of sufficient size.
I'm now in a one-party consent state and have a trusty-dusty digital audio recorder.
But it's more that if you come in and say that MySQL and PHP is good enough for everything, you're going to sound washed up. It might be true, but it's not good team chemistry when everyone wants to do one thing and one person keeps pulling them back. You don't even have to be 40 for this; 26 is "old" enough.
xD
I'm a 43 yo autodidact + BS EE/CS. Haven't had a problem except for resume gaps when doing side-hustles and unnamed startup consulting for too long, HR at shops raise their eyebrows. When it gets to in-person interviewing, I may have a leg over with ~10 years of neanimorphism, look somewhat between a neohippie artist and an idle trustfunder (definitely neither, LOL!), and (obnoxious bragging here) date college students which might help with youthful-seeming attitude.
Oh and worked on nuclear reactor simulators, infosec research, compilers, industrial mining embedded systems, HPC biomedical informatics, and just about every permutation of AWS/hybrid cloud startup scaling (Prod Eng/SRE). Rust, Haskell, C, Ruby, TS/Elm, and so on.
There's always learning, new approaches, and shifting standards to handle.
The more you know, the more you know that you don't.
Buying into one's own ego / being the office jerk are the biggest enemies in high-productivity tech. Relentlessly resourceful go-givers tend to win out in the long-term as the most valuable employees because the big name celebrity rockstar whatever tends to write checks their hubris can't cash.
As a frontend dev, I don't think complexity is the issue. I _love_ the new tools at my disposal and am grateful that time has done away with many issues we used to have, such as poor cross-browser compatibility.
Rather, I think the main problem has to do with layers. The bottom layers - the hardware, the kernel - they just work. It's the topmost layers that are the problem - there's a constant battle with dependencies, configurations and tools.
I'm sure that a lot of this frustration would go away if people weren't forced to do yak-shaving every time they wanted to develop an app.
I complain here and everywhere about the insane complexity in modern-day web app dev.
The truth is that, after you learn the 20 new tools/technologies you'll need to become semi-competent in only one stack, it won't seem like such a massive shift anymore.
I think competition is not that fierce -- honestly speaking as I can -- but that's for corporate jobs, etc.
And you _have_ to be competent or good or really good if you're older.
Else, you're just going to sound...like you sound -- old and washed up.
Not saying you are, or I am, but once you're 25+, if you bring the 'Get off my lawn' vibe, your 27-yo manager-to-be is gonna smell it a mile away, and he's gonna be feeling awkward enough already.
So I think you can be fine, but you gotta actually know what you're doing, and you have to get/be modern.