17 ms·
I look at the skillset between when I was 25 and now (30) and it's astounding. I can't imagine what the difference between 50 and 25 will be. If you're hiring
by pc86 10y ago
I look at the skillset between when I was 25 and now (30) and it's astounding. I can't imagine what the difference between 50 and 25 will be.
If you're hiring 40-60 year olds you cannot simply hire a 25 year old and get an "acceptable tradeoff of competency" unless you didn't need anything close to that competency in the first place.
Also if you're 50 and are relying on a new job's retirement program you're probably in for a rude awakening about when you can retire. That should be pretty close to set by that point. If it's not, the difference between matching 4% or 3%, or 75% match v. 100% is not going to be shaving more than a few months off your working career.
> They have less primary & secondary education relevant to today's enterprise issues.
I'm pretty knowledgeable about paid search and social but I don't think my Political Science degree has anything to do with that. To imply that someone's age precludes them from understanding paid search, mobile advertising, or social is the very definition of ageism.
- epalmer 10y agoI'm 63 with a BS in Chemistry and MS in Environmental Systems Engineer. I was a student teacher of microbiology when I was in graduate school. I started coding fortran in HS about 1969 or 1970. > I'm pretty knowledgeable about paid search and social but I don't think my Political Science degree has anything to do with that. To imply that someone's age precludes them from understanding paid search, mobile advertising, or social is the very definition of ageism. I run 134+ branded sites (and maybe 20+ other misc sites) some of which do extensive search marketing (extensive for a university). I am a digital native as much as the next person regardless of age.
- overcast 10y agoSorry, you run 154+ sites?
- epalmer 10y agoSure do.
- deleted 10y ago[deleted]
- overcast 10y agoI thought I was busy with ~10.
- epalmer 10y agoIt is not that bad. All are in a push CMS. We have a staff for content and UX. Many sites are small. Probably total 15,000 pages for all sites. These are univeristy sites so they are not complex apps. But there is a lot of backend code and middleware for pushing files to the CDN and to an xml database.
- logicallee 10y agoAll right. I'll be honest, I forgot what thread we were on, I was just in awe at all of the sites you run. My next thought was, "man, I wish I could use some guy like him, but he is just too expensive." One thing is for sure: there are definitely, 100%, no-questions about it, over 1 people who can be reached and who, at least for a few months, would take over 15,000 pages and 154+ sites. (An early 20s hacker). For under $30,000. That excludes nearly everybody: but not everybody. There is 1 person you can find who can do it. However, that one person is not going to be over 50. Over 50 people "aren't stupid" and are not going to do that for you for $30,000 and no other compensation. You can say under twenty people will be "stupid enough" that you can find someone to do it. But more accurately, they have different motivations. There's nothing stupid about working for $30,000 doing a job that's worth half a million, when your friends are earning $20,000 as barristas at starbucks. People's lives change over time. . . .
- nostrebored 10y ago"There's nothing stupid about working for $30,000 doing a job that's worth half a million, when your friends are earning $20,000 as barristas at starbucks." That's patently false. Undervaluing your labor because your friends work in a poorly compensated industry makes no sense. If anything the money you are earning when you are younger is more important to secure for ROI purposes.
- emcrazyone 10y agoso you're the exception to the norm; you're one data point against... ;)
- epalmer 10y agoYou might be right. I run circles around some of the youngsters I work with. Yet I still feel like an imposter.
- skrebbel 10y agois he though? i mean, are you sure about the norm? meet a young colleague who doesn't understand search, you'll say "he has no clue about search". meet an older colleague and you might say "he's too old to understand search".
- deleted 10y ago[deleted]
- saghm 10y agoReminds me of http://xkcd.com/385/ http://xkcd.com/385/
- blueatlas 10y agoI am 55, CS degree, and also a digital native. I run a digital agency. In this past year, I've been the technical decision maker for development efforts for over 20 web sites/applications, full stack. I can work with decision makers, and I can deep dive to any place in the web stack. I was the technical lead on a cloud deployment for a $1bn government contractor. I have a business partner and am also in the early stages of a SaaS startup. My point. Nobody will ever dictate what I can and cannot do in this complex, wonderful, and growing digital space. Ever.
- otakucode 10y agoThe norm? Which would be the general public? I think you will find anyone who can solve an equation is an exception to the norm. A computer programmer of ANY competence, even an amateur 12 year old, is 3 standard deviations outside the norm. And if you're going to restrict your norm to just computer professionals... you'd best run some numbers before making assumptions.
- nkassis 10y ago"unless you didn't need anything close to that competency in the first place." I think that's a key thing to look at. There is only so much space at the top of the experience chain in most jobs. I doubt most companies need more than 1-2 senior software devs per 5 software devs.
- xapata 10y agoMost companies are structured as a pyramid. Depending on the career path, it's about 1/5th the population for each rung up the ladder you climb. Not everyone should expect to climb to the top.
- skwirl 10y ago>I look at the skillset between when I was 25 and now (30) and it's astounding. I can't imagine what the difference between 50 and 25 will be. I completely agree (I'm 32), but what is worrying is the possibility of a fundamental shift that doesn't occur within individual companies but rather manifests itself as a new industry of sorts, and then a slow decline of the industry we're in right now - a paradigm shift, for a lack of a better term. That one is harder to detect until it's blatantly obvious, at which point the early practitioners in the new industry are now the senior engineers and newly minted college graduates are overwhelmingly starting their career in the new industry. Developers in the old industry have to cling on to whatever jobs are left or start over. My uncle is a good example of this - he's in his 50s and has spent most of his career working in what are now ancient IBM technology stacks (ever hear of RPG?) He saw object oriented programming as snake oil and a passing fad. When there were finally no jobs left near him for working in this IBM stack, he begrudgingly learned Java/C#/JavaScript/SQL and took a major pay/prestige cut basically starting over. It's not just technology stacks - even the methodologies in this industry seem to undergo radical changes every few years (for better or worse). What experience ends up transferring to the new industry? Soft skills, perhaps, but lots of people outside either the old or new industry have good soft skills experience, so what do you bring to the table that they don't? This isn't an "age problem." It's something deeper than that. If my uncle had jumped ship from his IBM world and into e-commerce in the 90s, which he was perfectly capable of doing, he would probably be a senior leader somewhere right now. But how could he have known? When the .com bubble burst, he probably felt vindicated in his decision to stay put. How confident are we that the web and mobile development that most of HN does today will be big in 2035? I'm not very confident at all. But how do I recognize when to jump ship? edit: grammar
- judahmeek 10y ago> It's not just technology stacks - even the methodologies in this industry seem to undergo radical changes every few years (for better or worse). If this is the case, then when someone entered the workforce has absolutely no relevance. What is relevant is staying current. It is absolutely ageist to assume that a 50 yr old is going to have more trouble staying current than a 30 yr old. > How confident are we that the web and mobile development that most of HN does today will be big in 2035? I'm not very confident at all. But how do I recognize when to jump ship? Thankfully, these days we have data scientists who examine trends in framework and methodology assimilation for fun and publicity. We have metrics like GitHub stars, Stackoverflow questions, and Google Trends to clue us in on the popularity and profitability of new ways of doing things.
- ____nope 10y agoI think the companies that hire an army of 23-25 year olds are planning to fail fast anyway. Why bother trying to recruit older, more senior talent that is going to expect higher benefits if the skills that they bring to the table vs. a 25 year old (knowledge of scalability, long-term decision making, planning, deep technical knowledge, etc.) aren't going to be used unless the company survives the first few years?
- andrewflnr 10y agoI was with you until the straw man in the last sentence. No one here is suggesting that age "precludes" you from understanding modern marketing media, only that it's less likely. Whether that's true or not is a question of actual data, not broad statements about ageism.
- peteretep 10y ago> If you're hiring 40-60 year > olds you cannot simply hire > a 25 year old and get an > "acceptable tradeoff of > competency" I'm a much better developer than I was 10 years ago, and I was pretty damn good then, but even when I'm 50, there will be people whose talent and ways of thinking about programming at 25 will be much superior to mine. And every year, my intuition about what constitutes bloat vs developer convenience, and when to just throw hardware (physical or cloud) at a problem that could be fixed via developer time, gets slight slightly more out of date.
- mikekchar 10y ago> I can't imagine what the difference between 50 and 25 will be. I think the problem we run into is that neither can most people. > If you're hiring 40-60 year olds you cannot simply hire a 25 year old and get an "acceptable tradeoff of competency" unless you didn't need anything close to that competency in the first place. And, again, the issue is that most people honestly believe that they don't need the extra competency. I work in a relatively enlightened group. People treat me with considerable respect and I feel that they value my experience (I'm knocking up against 50 years old). Even still, if I say, "You know what, I've tried that before a few times and it never seems to work out" nobody will accept it as an answer :-). These young guys all want/need to make their own mistakes. Sometimes I've even run into situations where people are doing considerable damage to their careers by making bad choices. Explaining the situation often makes them very, very unhappy. You end up feeling like the dad on a team of teenagers where everyone deep down loves and respects you, but day to day hates your guts :-). Since the field is growing so fast, we have this influx of young talent. They just can't see beyond where they will be in 5 years. Just the other day I saw an ad on Youtube for some programmer mill -- "I took a 10 month course and now I'm living my dream," kind of BS. Everybody wants to think that they are doing an awesome job and we have pushed back the bar for awesome a fairly long way. There's an expectation that you can do a boot camp, work for a year or two and then it's easy street from there. The reality, of course, is that 30 years on I'm still reading and hacking and struggling and experimenting and learning -- and I've been doing it for 30 years. I look in awe at some people in the industry and wonder if I will be able to gain that kind of competency before I retire. I think if I could sum up the advantage of being more experienced it would be to watch the classic movie, "The Seven Samurai", note who survives to the end, think about why they survive and remark on what they plan to do next.
- pc86 10y ago> You know what, I've tried that before a few times and it never seems to work out" nobody will accept it as an answer Because that's hand-wavy nonsense about "a few" data points. If you said that whatever you're discussing never worked out because of A, B, and C, and at least once of those is still an issue, then it would probably be accepted.
- maverick_iceman 10y agoI think you're suffering from selection bias.
- ido 10y agoI look at the skillset between when I was 25 and now (30) and it's astounding. I can't imagine what the difference between 50 and 25 will be. While it's true that there's some new tech/tools coming out, stuff doesn't necessarily change that much...I started working as a programmer at 18 (I'm 33 years old now) when the popular new thing was java. In between I used many different languages and tools (c, c++, python, matlab, js, haxe, as3, in no particular order & probably some that I've forgotten) but now I'm using c# which very in-vogue in my line of work (game development, due to the popularity of unity) and it was a virtually seamless transition from java (I actually started using c#/.net in 2009 as a tools programmer independent of unity). EDIT: nevermind, I realize now you meant you improved drastically in 5 years, not that the tech field has changed drastically.
- mseebach 10y agoThere are fundamentally two kinds of experienced people: Those with n years of experience, and those with m years of experience n/m times (where n >> m). Part of the only-somewhat-mythical recently-lost middle class compact was that you you train to do something, then work the rest of your life doing that. The former kind, the people who trained as electrical engineers in the 70s (because computer science wasn't invented then), then kept their skills up to date, will have very little trouble finding interesting and well-paid things to work on. The people who still think in terms of mainframes and consider tab-completion uncomfortable magic[1] won't. When, on top of that, they subscribe to the other part of said middle class compact, that your salary is supposed to keep going up (above inflation), then you have a recipe for disappointment. Is there embarrassing ageism in tech? Undoubtedly. Does ageism explain all of why elder techies on average have trouble finding employment in 'new tech'? I strongly doubt it. 1: The number of ostensibly highly experienced Unix (retrained on Linux) system admins that I have personally, not even exaggerating, promise, taught to use tab completion in Bash in this decade is depressing.