3 ms·

A lot of older programmers seem to think they have 20 years of experience, when they only have the same year of experience 20 times. If you don't keep up to da

A lot of older programmers seem to think they have 20 years of experience, when they only have the same year of experience 20 times. If you don't keep up to date and current, it's not ageism.

flukus 10y ago
True, but this applies at every experience level, not just older people.
sidlls 10y ago
You represent the other extreme with your comment. Very few software projects have more than two or three years of "experience fertility," for the kind of experience you mean. There's a difference between someone who can't even last a year to get a project from prototype to some semblance of maturity and someone who wants to move on after one to two years when a project reaches the point at which maintenance overtakes new development. What's the difference between somebody who works on four different projects over 8 years for company X and somebody who works on four different projects for four different companies over the same period, in this context?
- jimmywanger 10y ago
  Nothing different between working at the same company for different projects, and working at different companies. Maintenance work is easy, less time consuming, and frankly mostly requires less effort. If you fall into that trap, and end up maintaining a large system that is slowly becoming obsolete, you're not building up more skills. A lot of older workers (and I am one of them) end up doing that cause that's the easy path, the one requiring no effort at all. And that leads you to becoming unemployable.
deleted 10y ago
[deleted]
drtse4 10y ago
> A lot of older programmers seem to think they have 20 years of experience, when they only have the same year of experience 20 times. A lot of younger programmers seems to think they have 3 years of experience, when they only have the same month of experience 36 times. Experience is made up by the experiences you had, if you have never worked in a proper environment or never actually tried to improve your craft, years doesn't matter much. And the myth of "being up to date", it can mean different things for different people. Sadly sometimes it just means that you need to have played with the latest fad that will disappear in a few years. In that case i'd prefer someone that's not up to date but can learn something different and it's used to do things the proper way.
- jimmywanger 10y ago
  I agree, a lot of younger programmers think they have 3 years experience when they've had the same month of experience 36 times. And this is not a dig against old people per se. But it's the sunk cost fallacy. If you've only been doing something for 3 years, and it's wrong, it's easier to convince them that it's wrong, vs. if you've been doing something for 20 years, it's a lot harder to convince somebody that they're doing it wrong. Especially if they've been successful doing things their way for 20 years.

A lot of older programmers seem to think they have 20 years of experience, when they only have the same year of experience 20 times. If you don't keep up to date and current, it's not ageism.

flukus 10y ago

True, but this applies at every experience level, not just older people.

sidlls 10y ago

You represent the other extreme with your comment. Very few software projects have more than two or three years of "experience fertility," for the kind of experience you mean. There's a difference between someone who can't even last a year to get a project from prototype to some semblance of maturity and someone who wants to move on after one to two years when a project reaches the point at which maintenance overtakes new development. What's the difference between somebody who works on four different projects over 8 years for company X and somebody who works on four different projects for four different companies over the same period, in this context?

jimmywanger 10y ago
Nothing different between working at the same company for different projects, and working at different companies. Maintenance work is easy, less time consuming, and frankly mostly requires less effort. If you fall into that trap, and end up maintaining a large system that is slowly becoming obsolete, you're not building up more skills. A lot of older workers (and I am one of them) end up doing that cause that's the easy path, the one requiring no effort at all. And that leads you to becoming unemployable.

deleted 10y ago

[deleted]

drtse4 10y ago

> A lot of older programmers seem to think they have 20 years of experience, when they only have the same year of experience 20 times. A lot of younger programmers seems to think they have 3 years of experience, when they only have the same month of experience 36 times. Experience is made up by the experiences you had, if you have never worked in a proper environment or never actually tried to improve your craft, years doesn't matter much. And the myth of "being up to date", it can mean different things for different people. Sadly sometimes it just means that you need to have played with the latest fad that will disappear in a few years. In that case i'd prefer someone that's not up to date but can learn something different and it's used to do things the proper way.

jimmywanger 10y ago
I agree, a lot of younger programmers think they have 3 years experience when they've had the same month of experience 36 times. And this is not a dig against old people per se. But it's the sunk cost fallacy. If you've only been doing something for 3 years, and it's wrong, it's easier to convince them that it's wrong, vs. if you've been doing something for 20 years, it's a lot harder to convince somebody that they're doing it wrong. Especially if they've been successful doing things their way for 20 years.