Earlier quoted context omitted.
> So just stay relevant? The point of age bias isn't bias against people without relevant skills, its an actual bias against person of certain ages. Our industry is ripe with stories of folks with extremely relevant skill sets not getting jobs after a certain age (50 seems to be common). There is some (unintentional I'm sure) age bias even in the response of "stay relevant" as if the implication is that older devs do…
I don't believe that most anecdotal claims of age bias are truly a bias against someone's age, but rather a bias against someone who had a long tenure at a single company perhaps with a single technology on a single product development effort. It looks like age bias because you may be 50, but you worked on the same thing for 25 years. I don't think the industry is nearly as ripe with unemployed and relevant 50+'ers a…
I'm not sure if this accounts for 0.1% or 99% of alleged "age bias" incidents but I agree with you: this is most definitely a bad thing for a developer to do to themselves.
I would be very, very skeptical of a prospective employee with a resume like that.
On the other hand, I'd think very highly of a prospective employee with a resume like that looked like that and had additional open-source or other programming projects they'd contributed to. I'd think, "This person loves to code, and has been pushing themselves to grow and diversify their skills despite being stuck in a daytime coding job that encourages no such thing..."
What do you think? What if anything would sway your opinion of somebody that has been maintaining a PHP4 app at BigHugeBoringCo for the last 10 years?