81–90 of 362 posts
Earlier quoted context omitted.
> Honestly I don't get the obsession with recent grads. They will work more hours for less money. This is nothing new. My first job out of university in the early 1990s was for one of the "big" consulting firms. 50-60 hour work weeks were the norm. I made decent money (they paid overtime) especially for a first job, but I wouldn't do it at my age now with a family and kids.
Why is there a belief in this industry that working more hours == productivity? Arguably a more experienced developer could do the same work (if not better) in less hours. The right to not work 12 hours a Day shouldnt be something that is earned with age. If a team is consistently required to put in unreasonably long hours it’s either due to being understaffed or poor planning. Both are a recipe for disaster...
Lack of manager ability to measure productivity based on anything else. Between POs, BAs, business representatives, and IT managers there are a lot of people who don't seem to be able to grasp why two relatively simple to describe tasks can require such vast differences in time. So it becomes hard for them to judge if their developer is wasting their time or not (and let's not even begin on overall lack of trust to begin with), so the only fall back measure is if they have their butt in the seat and appear to be working. And even if you are lucky enough that everyone you directly deal with either understands the basics on why sizing varies so greatly or able to accept it without question, you still have to deal with middle managers walking the floor who measure productivity the same as they would in a factory. And if you are lucky enough to not even have this problems, you still have to deal with cultural norms set in party by all the jobs which aren't as lucky.
Earlier quoted context omitted.
I don't think I get your point. Are you implying that trashtalking hip design trends is grounds for age discrimination? Or that older employees give an amount of pushback on design decisions that makes them literally unhirable? I can trashtalk the design on everything I've directly worked on more accurately and damningly than things I read about online that seem like bad ideas. And I do. Do you think because I find f…
The fact that everyone who's offended by the post is claiming that React is a "hip design trend" kind of reinforces the point, doesn't it?
a) Getting pushback on your idea is not necessarily someone taking offense
b) Casting react as a "hip design trend" is not - in and of itself - a statement about it's fitness for a purpose. It's a statement about popularity, and highly visible things should expect criticism.
c) Even if trendy is meant to disparage the tool as nothing more than a flash in the pan, I think that gets to my (unaddressed) point about hyperbolic language in unimportant discussions.
e) "The reaction proves the point" can be applied to any disagreement, therefore it doesn't reinforce a point without more substance that they're meaningfully connected.
d) It's still unclear what your point was supposed to be. My ask for clarity was not facetious, so far I'm only responding to the point I can infer but find flimsy enough that I preemptively conceded you might be getting at something else.
Earlier quoted context omitted.
Readers: what's your exit strategy? You probably need one.
What are some common exit strategies in the industry? It seems like early startup options for employees are more of a lottery ticket than retirement plan.
Earlier quoted context omitted.
> Honestly I don't get the obsession with recent grads. They will work more hours for less money. This is nothing new. My first job out of university in the early 1990s was for one of the "big" consulting firms. 50-60 hour work weeks were the norm. I made decent money (they paid overtime) especially for a first job, but I wouldn't do it at my age now with a family and kids.
Why is there a belief in this industry that working more hours == productivity? Arguably a more experienced developer could do the same work (if not better) in less hours. The right to not work 12 hours a Day shouldnt be something that is earned with age. If a team is consistently required to put in unreasonably long hours it’s either due to being understaffed or poor planning. Both are a recipe for disaster...
Earlier quoted context omitted.
The facebook CEO is very famous for his quote by the way. https://www.cnet.com/news/say-what-young-people-are-just-sma...
Yeah, Zuck was a jerk in 2007. I suspect even he would admit that. To be fair, though, I was an even bigger jerk at that age and still am.
Excellent news! Up until age 39, I was never not given an offer after interviewing. Now after 40, my offer rate has dropped to 1 in 14. So much for the claims that there is a shortage in tech. So crazy.
I'm not saying you're this person, but a lot of people making this claim are also the people that seem argue with literally everything. They always claim they know better. "Oh your team of 8 has spent the last 12 months building this complex webapp with React? Gosh darn millennial hipsters and their FRAMEWORKS. I could have built it with jQuery in a week, and still had a nickel leftover for the trolley!" Yes I've exa…
You put your scenario in disparaging terms, but consider another way to look at it:
- They may well actually know better. Listen, ask questions and learn. - You say arguing, but you most definitely want people who think critically about literally everything. (You also need people who will get on board with the plan even thought they don't necessarily agree with all the details.)
Earlier quoted context omitted.
Age discrimination in tech is dumb. I've got a dev 30 years my senior sitting across from me and I guarantee he will code circles around 90% of the devs on HN, and 100% of the new grads getting jobs at big tech (and will until he dies). He's got a huge amount of knowledge in programming, our domain (NLP), he's fast, thorough, and thoughtful. Honestly I don't get the obsession with recent grads. They are basically use…
Some of reasons I’ve seen for ageism in startups are cost and “not a culture fit”. Cost I understand, but I believe more experienced people end up being cheaper in the long run when you account for speed, correctness, and long term maintainability. The culture piece stems from the “would I get a beer with this person” and will he/she work as “hard” as a younger candidate with less responsibilities. Startups need to s…
Excellent news! Up until age 39, I was never not given an offer after interviewing. Now after 40, my offer rate has dropped to 1 in 14. So much for the claims that there is a shortage in tech. So crazy.
If people want to filter applicants based on age, it's pretty simple to do so before the interview stage.
Earlier quoted context omitted.
Readers: what's your exit strategy? You probably need one.
Age discrimination in tech is dumb. I've got a dev 30 years my senior sitting across from me and I guarantee he will code circles around 90% of the devs on HN, and 100% of the new grads getting jobs at big tech (and will until he dies). He's got a huge amount of knowledge in programming, our domain (NLP), he's fast, thorough, and thoughtful. Honestly I don't get the obsession with recent grads. They are basically use…
My company has found a competitive advantage by doing blind hiring and getting super talented people (sometimes older, sometimes female) that other companies have undervalued.