As a general rule: Old enough that I feel that it would be rude to ask their age. Wikipedia entries for three of them indicate 41, 52, and 64, though.
Please don't treat old timers any differently than anyone else. If you're comfortable asking someone in their 20s what their age is, you should figure out what is making you hesitate for someone past a certain perceived age.
Ask HN: How old were the most talented software engineers you've met?
91–100 of 186 posts
Re: Ask HN: How old were the most talented software engineers you've met?
#92Earlier quoted context omitted.
Same story here. The most talented engineers I know are either in their early 20s or in their late 40s/50s. Of course it's for different reasons. Something many people don't want to admit is that a lot of talent comes from practice and experience, and someone in their 40s is much more likely to have 20+ years of experience than someone in their 20s. The early-20s geniuses I know are talented for different reasons. Th…
>The ones I am thinking about are people who pick up new things absurdly quickly; pick up on patterns very easily; have general experience in enough domains to make quick connections; etc. That's my experience as well. Generalists are often the most productive people. A good generalist can often grasp the whole system faster than a niche programming language specialist. And you usually don't need those niche programm…
PL specialists are also pretty good generalists. I mean, what hasn’t Jeff Dean done and do people even remember that he has a PL PhD anymore?
Re: Ask HN: How old were the most talented software engineers you've met?
#93Earlier quoted context omitted.
Same story here. The most talented engineers I know are either in their early 20s or in their late 40s/50s. Of course it's for different reasons. Something many people don't want to admit is that a lot of talent comes from practice and experience, and someone in their 40s is much more likely to have 20+ years of experience than someone in their 20s. The early-20s geniuses I know are talented for different reasons. Th…
>The ones I am thinking about are people who pick up new things absurdly quickly; pick up on patterns very easily; have general experience in enough domains to make quick connections; etc. That's my experience as well. Generalists are often the most productive people. A good generalist can often grasp the whole system faster than a niche programming language specialist. And you usually don't need those niche programm…
Mandatory plug: if you think you'd fit the bill and are keen to explore, find me through my HN profile. Bonus points for being anywhere in APAC, although I can refer you elsewhere too.
Re: Ask HN: How old were the most talented software engineers you've met?
#94Earlier quoted context omitted.
The ageism in SV has very little to do with actual talent and productivity and much more with how the team feels someone can handle themselves at happy hour.
I think there's three components to every employment position: - sufficient work ability, rarely an issue. - teamwork - at work interface, negotiating, empathy with others. be relentlessly resourceful and useful, but get yours too. - off-the-clock skills and interpersonal/appearance likability - a bunch of awkward single dudes can't say "no" to the socially-calibrated dude who goes out and convinces a bunch of attrac…
Re: Ask HN: How old were the most talented software engineers you've met?
#95Re: Ask HN: How old were the most talented software engineers you've met?
#96Re: Ask HN: How old were the most talented software engineers you've met?
#97Earlier quoted context omitted.
>The ones I am thinking about are people who pick up new things absurdly quickly; pick up on patterns very easily; have general experience in enough domains to make quick connections; etc. That's my experience as well. Generalists are often the most productive people. A good generalist can often grasp the whole system faster than a niche programming language specialist. And you usually don't need those niche programm…
As a specialist who is currently looking for a job, HR generally only seeks generalists. Almost all interview loops that have been standardized seriously prefer generalists. The mold doesn’t fit anyone and are just generic programming/system design questions that do not evaluate specialist skills and experience at all. PL specialists are also pretty good generalists. I mean, what hasn’t Jeff Dean done and do people e…
This is to say that I don't think you should use Jeff Dean as an argument for hiring PL specialists in generalist roles.
Re: Ask HN: How old were the most talented software engineers you've met?
#98Now it is people who consistently deliver high quality, well thought out software. The speed matters far less to me (or my clients). These are over 40.
Re: Ask HN: How old were the most talented software engineers you've met?
#99Earlier quoted context omitted.
Same story here. The most talented engineers I know are either in their early 20s or in their late 40s/50s. Of course it's for different reasons. Something many people don't want to admit is that a lot of talent comes from practice and experience, and someone in their 40s is much more likely to have 20+ years of experience than someone in their 20s. The early-20s geniuses I know are talented for different reasons. Th…
>The ones I am thinking about are people who pick up new things absurdly quickly; pick up on patterns very easily; have general experience in enough domains to make quick connections; etc. That's my experience as well. Generalists are often the most productive people. A good generalist can often grasp the whole system faster than a niche programming language specialist. And you usually don't need those niche programm…
I think as you gain experience you naturally become more of a generalist over time.
I've been a freelance developer for 20ish years and I would consider myself a generalist at this point, but it took many many years to get to this point.
Everything from learning the Linux basics, how networking works, various programming languages and web frameworks, database modeling, dealing with the ops side of things, and the list goes on and on. Basically I spent a majority of my life learning all of these things in a lot of detail, but most of it ended up being on a need to know basis.
Basically once you become somewhat proficient in something, you naturally start learning about some other related topic. Even today I still think I know almost nothing in the grand scheme of things.
Re: Ask HN: How old were the most talented software engineers you've met?
#100I spent a decade working with some very talented people in my mid-20s to 30s, and they aged along with me? The single smartest person I worked with, the guy who wrote a h265 decoder by himself and did Project Euler problems for fun, was also in his mid-30s and worked 4 days a week to spend more time with his family. He was a mathematician by background though, and they tend to peak early; intellectually I think he wo…