4 ms·
> without the hassles of things like kids to take care of That's not accurate. At 35 there are young kids, maybe even 45. At 50 they're pretty much independent
by joelbluminator 5y ago
> without the hassles of things like kids to take care of
That's not accurate. At 35 there are young kids, maybe even 45. At 50 they're pretty much independent, at least aged 10-12.
So actually, if you hire a 32 year old dev you should be more concerned about kids than if you hire a 50 year old.
So if that's the concern, only hire 18 year olds I guess, or maybe even 15.
- commandlinefan 5y agoActually if you hire 25-year-olds, they're probably going to start having kids right around the time you need them the most.
- Pokepokalypse 5y agoyeah, but the plan is: lay them off once they start having kids, and hire new 25-year olds. source: 25+ years experience in this industry.
- Ma8ee 5y agoThe spread is quite wide. I got my first kid at 45 and now almost 50 working 75% to take care of two kids the rest of the time. The flip side is that I have never been so focused during working hours as now. I’m getting quite much more done in six hours than I used to get done in eight or nine.
- joelbluminator 5y agoYes I feel more productive than many of the younger, childless colleagues at work. In fact I really don't like going to the office due to people talking WAY too much. I have 8-9 hours and then I need to pick up my kid, not using those 8-9 hours to the fullest is something I simply have to avoid. And incidentally my least productive days are the in office days.