4 ms·

With respect I think that those characteristics could equally apply to anyone - old, young or somewhere in the middle. I wouldn't say any of those are specific

With respect I think that those characteristics could equally apply to anyone - old, young or somewhere in the middle. I wouldn't say any of those are specific to people approaching their retirement age. For example I interviewed someone in their early 20s a little while ago who knew Angular 1 inside-out and to the absolute finest detail, but that is obsolete now that we're on Angular 6/React etc - they had never used modern Angular, Typescript or React... just good old Angular1 + JS. Did they stay relevant? nope. Are they old? nope. The benefit of the doubt for the early-20s person could be to just assume they don't know Angular6+TS because they were working on legacy code and didn't get the chance, but should I treat the early-20s person any different from a 60s person all other things being equal? nope. I am sure they could both pick up the new skills just as easily. I know a lot of retired people socially (parents/friends of friends, neighbors etc - alas not that many from work) who are still 100% as sharp as a tack - quick-witted, intelligent, energetic etc. It would be unfair to use their age as a filter based on assumptions of how they would perform in an interview based on how other entirely different individuals have behaved in previous interviews.

infecto 8y ago
100%. I am not suggesting these characteristics are only found in a specific age group. I am suggesting that I find this to be true the older someone is. I still would like to believe that the majority of the issues are not true ageism.
rightbyte 8y ago
Obsolete? Is this sarcasm? Angular 1 vs 6? Like, how can the burden of getting up to speed in a later version of the same framework even compare to that of getting your head into all legacy company code and how the coffe machine at the office is refilled? "Oh, .Net 3.5 you say? We do 4.0 here. We call you back." Coding has barely changed since the 60s. The screens are bigger. It's the programs that have evolved not the programmers really.
- mattlondon 8y ago
  My point I was trying to make was that not staying relevant in tech is not unique to "old" people. The early 20s person who went deep with angular 1 may not have "kept relevant", but that is no reason to outright reject them (or someone 30-40 years their senior) on its own. I am sure they (and "old" people) would easily be able to get up to speed. As you said, programming has largely remained unchanged at a fundamental level.
  - rightbyte 8y ago
    Fair enought. On another note I believe one fundamental reason some employers prefer younger employees is that they are easier to push around.
datavirtue 8y ago
"I am sure they could both pick up the new skills just as easily." Then what is the relevance of your harping on thier proficiency with slightly older same Ole crap tech?
- mattlondon 8y ago
  I was refuting the statement about older people potentially not "keeping relevant" in tech. My example was an early 20s person who was also not relevant in tech, despite not being "old". Not keeping relevant is not a problem related to age was the point I was trying to make, but actually applies to all ages equally.

infecto 8y ago

100%. I am not suggesting these characteristics are only found in a specific age group. I am suggesting that I find this to be true the older someone is. I still would like to believe that the majority of the issues are not true ageism.

rightbyte 8y ago

Obsolete? Is this sarcasm? Angular 1 vs 6? Like, how can the burden of getting up to speed in a later version of the same framework even compare to that of getting your head into all legacy company code and how the coffe machine at the office is refilled? "Oh, .Net 3.5 you say? We do 4.0 here. We call you back." Coding has barely changed since the 60s. The screens are bigger. It's the programs that have evolved not the programmers really.

mattlondon 8y ago
My point I was trying to make was that not staying relevant in tech is not unique to "old" people. The early 20s person who went deep with angular 1 may not have "kept relevant", but that is no reason to outright reject them (or someone 30-40 years their senior) on its own. I am sure they (and "old" people) would easily be able to get up to speed. As you said, programming has largely remained unchanged at a fundamental level.
- rightbyte 8y ago
  Fair enought. On another note I believe one fundamental reason some employers prefer younger employees is that they are easier to push around.

datavirtue 8y ago

"I am sure they could both pick up the new skills just as easily." Then what is the relevance of your harping on thier proficiency with slightly older same Ole crap tech?

mattlondon 8y ago
I was refuting the statement about older people potentially not "keeping relevant" in tech. My example was an early 20s person who was also not relevant in tech, despite not being "old". Not keeping relevant is not a problem related to age was the point I was trying to make, but actually applies to all ages equally.