Is it really because they're old? Or because they've established they are one trick ponies?
I've met young programmers who I wouldn't hire (were it up to me) for the exact same reasons most people wouldn't hire the stereotypical old programmer. 'Legacy' dudes from a time who seemed to understand bad code as a way to always retain a job because who else would understand the shit they do?
And then I've also met (and worked with) older programmers who taught me about the almost repetitive cycle of trendy functional languages, the types where I can literally have a two hour long philosophical conversation about design, extremely smart people I would hire.
I get the sense this is not entirely about ageism, but rather, the field itself has two different directions for growth.
I've met young programmers who I wouldn't hire (were it up to me) for the exact same reasons most people wouldn't hire the stereotypical old programmer. 'Legacy' dudes from a time who seemed to understand bad code as a way to always retain a job because who else would understand the shit they do?
And then I've also met (and worked with) older programmers who taught me about the almost repetitive cycle of trendy functional languages, the types where I can literally have a two hour long philosophical conversation about design, extremely smart people I would hire.
I get the sense this is not entirely about ageism, but rather, the field itself has two different directions for growth.