241–250 of 265 posts
Earlier quoted context omitted.
You are looking at it in black and white terms. Just because there is also a reason younger people might leave unexpectedly doesn't invalidate my assertion. And, having someone leave unexpectedly doesn't have to "tank" the company without still causing damage. Like I said, black and white terms...
Guess I hit a lot of sore spots...
Earlier quoted context omitted.
True, but companies don't care about those things, really, even in the supposedly developer-centric Bay Area. Just browse through any jobs thread or board, even (especially) the "Who's Hiring" HN thread. You're going to see a lot of "We're looking for an X developer" or "we're looking for a developer with Y years of experience in Stack X." Employers, even supposedly knowledgeable tech centric ones, routinely think th…
It's because most of the who's hiring on HN posts are small 2-3 people startups that desperately need a new programmer.. yesterday. They're not a team that can afford to bring someone up to speed, even if that person is amazing in programming other things. Which is really unfortunate.
Lots of folks commenting here on there not being many older developers around. Well considering there are at least 10x more developers now than there were 30 years ago, and people generally get into it when they're young, this is completely expected.
Earlier quoted context omitted.
Your age or birth date probably shouldn't be on your CV. Unless you think it's relevant to the job somehow, but it probably isn't. Not only should it not matter, but it's illegal for employers to ask about it or consider it in their hiring decision, so having it right there on your CV puts them in a bit of a tight spot. I think some recruiters will actually remove that type of thing before forwarding it on to the int…
Graduation dates need to be there for any role that involves a background check.
This is a market failing that anyone who is hiring can exploit. I've worked for a guy who hired young, smart guys without much experience who he felt had potential and who also had some 55+ year old developers who he thought could do things. He was one of the best managers I've had. So be smart and realise that people who don't fit into what you expect might find it a bit harder at some places to find a job and that…
Or hire remote, smart, Haskell developers from cheap countries.
I've found a pretty distinct lack of functional developer jobs in my region. Though I was surprised to find a local software company that has specifically recruited several Clojure developers.
Earlier quoted context omitted.
You are more likely to die soon, and if you have some unique understanding of how the company works, that would be lost.
And how is this supposed to be worse than hiring a series of youngsters, each not yet knowing how any company works, and then replace'em when they are just begining to get a clue?
The parent asserted there is nothing disqualifying an older person from being hired. I gave one reason, essentially that health declines when you age.
No one refuted my point, yet I get downvoted to oblivion. It kind of says something about older people if this is how they respond to critical thinking.
I can't say that this sort of response is unexpected, though, given my experiences with the older generations. They tend to be short tempered and unwilling to consider alternative evidence to their (foregone?) conclusions.
I guess that's another reason to avoid hiring older workers. They're likely to have a lot of hubris.
Earlier quoted context omitted.
Graduation dates need to be there for any role that involves a background check.
If someone is doing a background check and can't find out when you've graduated, then why bother?
There are voices that are stating there is a serious shortage of highly skilled tech workers in the Valley and as a result the H1B Visa quotas must be dramatically increased and policies amended to allow for foreign workers.
There are also regular claims of ageism in the Valley against people who are possibly not only highly skilled but also possess many years of real world, "rubber on the road" experience.
Are these two things not at odds with each other?
Earlier quoted context omitted.
Hm, depends on the business, I guess. Because from my experience, most business algorithms are proprietary and don’t have proper specifications. You can’t just use them somewhere else. You have to recreate them from scratch.
Probably because your devs didn't write them in stored procs like they should.