Source: my six year education and 41 year pro career that began under people who had once fought in WWII and I’m still way (WAY!) younger than the youngest founder of Apple (#8)
Source: my six year education and 41 year pro career that began under people who had once fought in WWII and I’m still way (WAY!) younger than the youngest founder of Apple (#8)
But the older workers don't have to stumble. They can learn the new platform. I'm an older worker and have done so many times over my career. It's not a huge deal -- especially because keeping up with changes in technology is a thing that everyone of every age has to do anyway.
When I have encountered age discrimination, it is usually because the org wants young gullible people with "passion" who put up with horrid working conditions, broken tech stacks and whacked out business models. The last thing they want is someone that has seen this three times and can point out the needless churn to support a CTO that doesn't know what they are doing.
True, although I wouldn't characterize it as being "jaded" as much as that experience makes the bullshit much easier to spot. And, generally speaking, the more experienced the dev, the lower the tolerance they have for bullshit.
And there are only a small handful of different paradigms. If you've been developing long enough, you've probably become competent in most, if not all, of them.
Going from C++ to eg Python or Java isn't much fun. Try going to Haskell or Rust, with the borrow checker.
I can switch to another programming language and write the For Loops and branching logic and all that jazz no problem. But there's often a lot of nuances that you just don't know and it takes a while to accumulate that knowledge. Those are usually referred to as "Best Practices" and there usually isn't a single source of truth document out on the Internet or anywhere to learn all of them.
They just come with experience and time, and maybe if you're lucky mentorship from a more experienced dev who knows those practices.
This is very clear to me having watched Java devs flounder their way through building JavaScript microservices using all of the old Gang of Four patterns and basically zero of the modern ES functionality.
How did you get your first job for each new platform that you learned? Let me guess—you knew somebody who helped you get your foot in the door. (Am I wrong?)
Why would you have to? You get the experience by working with the technology, just like everyone else. The older worker and the younger worker both need to have X amount of experience.
I don't see how this aspect is related to age at all.
> How did you get your first job for each new platform that you learned? Let me guess—you knew somebody. (Am I wrong?)
You're wrong. Connections are important for getting any new position, but connections aren't what got me "in" on a new platform. I've learned new platforms either (usually) on my own, or because working with the platform became part of a job I already had.
I still don’t see how learning a platform on your own got you past HR resume screening. Learning something via a side project over a couple of weeks is hardly the same thing as having multiple years of professional experience already.
Are connections always important for getting a new position? I doubt that a doctor needs to already know somebody at a hospital in order to get an interview … but I could be wrong about that, I guess.
Age matters because someone just out of college probably at least did their internship in whatever platform is popular right now. They also will probably accept lower pay and worse working conditions. So the older worker has little or even negative advantage if they’ve been using the “wrong” platform in their recent job and don’t have a strong personal network.
Not at all. They've been new projects, not rewrites of old ones.
> I still don’t see how learning a platform on your own got you past HR resume screening.
If I spent 3 years working with a platform on my own, that's still 3 years of experience with the platform.
> Age matters because someone just out of college probably at least did their internship in whatever platform is popular right now.
I don't understand this point. An older dev can also have spent a few years working with whatever platform is popular right now as well. Age doesn't enter into this at all.
I sense, though, that we're not fully understanding each other about something. Are you thinking that "3 years experience" is both a hard and fast rule and that it means 3 years being paid to work with it? Neither of those things are true.
From my perspective hard requirements turn out to be red flags more often than not. Asking for 6+ years in a single language kind of looks like you regret your tech stack. Requiring experience with project management software is a cry for help.