The second dev who took my breath away was a man in his late 40s who had consistently moved from companies as soon as they wanted to put him into management. He loved to code and was very good at it, but for some reason management wanted him to make room for younger hires (can anyone with more experience explain why that would be the case? This man has 20+ years of experience and loves to code, shouldn't he be more preferable to some kid?) so he was able to leverage his contacts he picked up as a consultant to change into high paying developer jobs. He was very understanding of how bad I was when I started out as a developer and was my mentor for a long time and his discipline still inspires me. It was an honor working for him, why people want to make such a good developer into anything but a developer, I'll never know.
Ask HN: How old were the most talented software engineers you've met?
71–80 of 186 posts
Re: Ask HN: How old were the most talented software engineers you've met?
#72Earlier 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…
That begs the question then, what happens to these early-20s geniuses once they are late 20s/30s?
Re: Ask HN: How old were the most talented software engineers you've met?
#73Re: Ask HN: How old were the most talented software engineers you've met?
#74One of them was one of the nicest guys I ever worked with, and his mind had a real understanding for what we do. When he learned something, he learned it well, and understood it deeply. A few weeks after being introduced to regular expressions, he had learned them to the extent where he could implement complex expressions, alongside knowing the differences between implementations in C#, PHP, and JavaScript. He was also very helpful, and despite being considered a junior-level dev was helping the more senior-level members of staff all the time.
Sadly, he had his own demons. One day we were all called into a meeting and were told he wouldn't be coming back. He had been battling drug issues that had resurfaced due to the heavy amount of painkillers he was taking for past injuries. Work had discovered that he hadn't done anything on a project he had been working on for a month, and when challenged on it he quit. This was a number of years ago, and by all accounts he's still without a job and lives with his parents.
One other is smart, but in a different way. I met him when he was a contractor at one of my old work places. At the time, he was brought in to do some Flash work, and after a work night out he told us that he didn't enjoy programming, so he made the decision a few years back to learn legacy tech. He had no interest in learning the best/most popular languages, only the most lucrative, because "you won't earn shit as a standard dev (in the UK)". I still talk to him a few times a year, and it's a gamble that paid off very well for him. He travels across the country and the continent working on things like ActionScript for shop kiosk displays, enterprise-grade Salesforce builds, and ColdFusion support and development. In terms of smarts, he's not the best developer in the world, but you have to have something about you to decide to go against the grain and back technology that many developers actively fight against.
Re: Ask HN: How old were the most talented software engineers you've met?
#75The 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 would have been capable of doing all the same things at 16 given time to learn the prerequisites.
From exposure to a lot of smart people at Cambridge, not just in software, I would say that the biggest impairment to turning smartness into results was depression. The second biggest was lack of common sense - it's very easy to be convincing as a smart person, and if you're convincing to yourself and others about some piece of unconventional wisdom that turns out actually not to work, it can go very wrong.
Re: Ask HN: How old were the most talented software engineers you've met?
#76Re: Ask HN: How old were the most talented software engineers you've met?
#77The kid was the most active person from the audience when it came to QA sessions after the talks. He asked genuine and interesting questions and spoke from his own experiences about building web apps and browser extensions.
I've never met anyone like him, even though I worked with some really good engineers in their 20s and 30s.
Re: Ask HN: How old were the most talented software engineers you've met?
#78As 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.
Re: Ask HN: How old were the most talented software engineers you've met?
#79Let me list few points:
# Tend to deviate from task and try to fix functional things which they think are not elegant engineering
# They are motivated to learn new technology so they will squeeze one without thinking about long term side effects like shipping delays and maintenance issue
# They think they will be productive working alone and mostly avoid collaboration which can be very costly down the road
# Failing to understand that trade offs to achieve business goals is a good trait to have
# Code maintenance doesn't motivate them like new shinier stuff
# Can slowly turn the business to be people dependent
# Going over board with code reuse and in the end introducing too many dependencies
Re: Ask HN: How old were the most talented software engineers you've met?
#80There was one programmer in his mid-20s that many co-workers thought was amazing, but I thought he was full of himself and produced overly complicated work that even he had trouble fixing and those around him found impossible.
Below that, I know of programmers who are very quick to learn things but just don't have the raw experience to really take care of things on their own yet.