4 ms·
Figured I'd create a throwaway account to chime in here. I'm 40+, and have to say the last few years (working for Fortune 100 companies) I am truly mortified a
by wjioertfhwoeirj 7y ago
Figured I'd create a throwaway account to chime in here.
I'm 40+, and have to say the last few years (working for Fortune 100 companies) I am truly mortified at the lack of skill in many of the younger folks I've worked with.
Also, generally speaking when I've had a younger boss I would say it's NEVER because they're qualified for the position. Generally it seems they've been able to pull the wool over their managers' eyes. Don't get me wrong, they have no bad intentions. All I'm saying is confidence can only get you so far in technology.
- mixmastamyk 7y agoI don’t find the comments complaining about older workers very helpful to be honest. Nor those complaining about younger ones either. Substitute white/black or rich/poor to highlight.
- deleted 7y ago[deleted]
- fit2rule 7y agoI've been a professional developer since I was 13, in the sense that was when I sold my first commercial product, some 36 years ago. I've gone from being the wunderkind to being the over the hill grey beard, and I've seen some shit. What I think happens is that every 4 or 5 years, there's a cycle of devolution. The new kids in school want to be that wunderkind - they choose therefore to ignore the wisdom of their elders and forge ahead into the darkness of their own knowledge with the light of their own hubris to guide the way. Many times, this is more than enough to build something great - often though, it results in failure. But, every year, a new round of developers hits the scene, fresh from boot camp. These bring new (old) ideas to the scene, rebranded perhaps, refactored perhaps. This somehow has a devolutionary effect on the industry as older developers get moved off the production seats into management, and there isn't an effective turnover to the new guys, who then spend a few years re-inventing things and re-gaining the experience of the previous guy. Things get re-invented. Regurgitated. Recycled. Eventually, a kind of stability occurs - and the new programmer becomes the old guy. The seats get changed again, and we go through the cycle again. Oddly enough, as someone who has gone from being the 13-year old wunderkind and is now the near-50 old guy, the only way I've found to survive this cyclic regurgitation is to stay focused on the user. Nobody cares if the user is young or old - what matters is if they're using something you built. Ageism is real. I started my career with a healthy dose of it - although in the 80's it was a lot more common to have respect for ones guru's than it is today, I nevertheless didn't want to know a lot of the 'obvious' wisdom of my elders - and now I'm 10 years away from retiring from the career, seeing it from the other side of the fence, there is a great deal of 'obvious wisdom' I see the youth of the technology world today clearly ignoring, and pretty certain they're going to re-invent in a few years time, subjectively and objectively. In my opinion, ageism happens because its hard to train people who have just escaped the hell of modern education, and all they want is the freedom to apply their skills and develop themselves, and their identities as skilled workers. Its hard for an old person to care about the stupidity of youth, because after all - if you've got the experience - you probably had a healthy dose of it too, and well .. you came out okay right? If we want to deal with age-related complications in this industry, we should address the source of the problem: educating people, and being educated by people, is hard.