Earlier quoted context omitted.
I attended a lecture last week, older people were one of the topics that got touched. Instead of having old employees teaching the younger, he told a story of a business requiring old people to receive fresh young employees as their mentor.
I'd like to hear more. What are the benefits of this arrangement? Is it merely an organizational statement that over-30's are worth less and need remedial training? What was the rationale? What was the group discussion like? What do you think about it?
Show HN: Hire an Oldster
181–190 of 308 posts
Re: Show HN: Hire an Oldster
#182I was recently working with an older developer. I don't know, maybe of 65 or 70 years. He was working on aerospace network intrusion detection systems, and I was helping him set up a simulation system. He was slinging around low-level computer architecture terminology, while I was quickly trying to access what I remembered from a college class 15 years prior, just to keep up with the conversation. Older programmers a…
I feel like in the startup space a lot of young people just aren't exposed to just how good highly experienced engineers can be. As a result, they end up just hiring the best youngsters they can find (and afford) and dismiss a lot of people as dated. It's just breathtaking when you watch an experienced engineer slap together a well architected, highly optimized project that passes all tests on the first try. They eve…
Where "proper" is critical. I've had a lot of managers, but few effective ones. And almost none who led the department. I found my mentors in other departments. It's a real shame, since a great manager will do more for learning and quality of life than anything else, I think.
Re: Show HN: Hire an Oldster
#183Should there be sites that zone in on a particular discriminating aspect of a person? Hmm, like www.hireanoldveteran.com for old veterans that are having trouble looking for jobs.
Re: Show HN: Hire an Oldster
#184I was recently working with an older developer. I don't know, maybe of 65 or 70 years. He was working on aerospace network intrusion detection systems, and I was helping him set up a simulation system. He was slinging around low-level computer architecture terminology, while I was quickly trying to access what I remembered from a college class 15 years prior, just to keep up with the conversation. Older programmers a…
I feel like in the startup space a lot of young people just aren't exposed to just how good highly experienced engineers can be. As a result, they end up just hiring the best youngsters they can find (and afford) and dismiss a lot of people as dated. It's just breathtaking when you watch an experienced engineer slap together a well architected, highly optimized project that passes all tests on the first try. They eve…
Re: Show HN: Hire an Oldster
#185An oldster in HN world is someone over 32, right?
Bar chart, kinda looks that way: http://hn-stuff.appspot.com/poll_chart/build/?thread_id=2175...
Re: Show HN: Hire an Oldster
#186Earlier quoted context omitted.
More like, I won't "hire" him. Hiring is a two way street. Always ask about how much overtime is expected from a job during interviews. If you don't believe in >40 hour work weeks, except maybe under rare conditions, then don't "hire" your prospective employer.
But once a recruiter has this type of experience with a few older candidates, they will be more likely to discount older candidates in the future, regardless of whether those later individuals were willing to do 60+ hour weeks or not.
Re: Show HN: Hire an Oldster
#187Earlier quoted context omitted.
> unwilling to run the same 60 hour gauntlet that a 25 year old _can_ etc. Older people _can_ run 60 hour gauntlets. We're just wise enough to know that it leads to no good outcome.
That wisdom makes you of negative business value to your manager, since he still believes 60-hour gauntlets are an intrinsic part of being on time and under budget. Hence, you won't get hired.
Re: Show HN: Hire an Oldster
#188Earlier quoted context omitted.
It 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.
All 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 un…
The worst case[0] is that they don't show up the next day and you are SOL.
0. Assuming they don't actively try to sabotage the company that has been exploiting them.
Re: Show HN: Hire an Oldster
#189Earlier quoted context omitted.
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…
>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…
for how long ? I dont blame him for reading about C++ in 1989 and saying "hrmmmf! hogwash!". But in 1995 ? in 2000 ? It sounds like he got set in his ways, and how is that NOT an "age problem" ? I'm also 32, and I'm getting slightly more set in my ways as I get older.
> he begrudgingly learned Java/C#/JavaScript/SQL and took a major pay/prestige cut basically starting over.
well, had he had an open mind and not shunned new things, he might be a Herb Sutter today. Or even in IBM, had he bet on a different "horse", and moved into As/400 or whatever other IBM technologies there are, he could be earning more than a C++ programmer, knowing some obscure proprietary IBM language and having 20+ years experience backing it up. I've heard of guys like that making $100+/hr because only a few people in the world can do it.
I think his story is one of mismanagement of intellectual capital. Maybe it's naive of me, but I dont see how you could be in software engineering for 30 years and not be worth at least a million, especially from his era. Did he invest in IBM or any tech companies at all ? How could you not see everyone making money in the dot-com era and not be a part of it ?
Re: Show HN: Hire an Oldster
#190I'm 40, in tech years that's like 1000. I also see value in hiring experience but explicitly factoring by age discriminates against a protected class in the USA. I think a lawsuit is in my future if I use this for placement at my company. Of course, if you simply rebranded to talk about "experience" rather than "age" then solvelem probbed. Also, age != experience != skill.
I'm 40 and don't feel that way at all.