Live data from Hacker News

Ask HN: Is programming a “young person's game”?

news.ycombinator.com

31–40 of 151 posts

Re: Ask HN: Is programming a “young person's game”?

#31
I started University at 24. Couldn't program, was quite bad at math. Learned logic the hard way, by grinding it. I'm 30 now, I'm very good at both math and programming, even published a paper. But I didn't do a PhD, turns out that I don't like academia.

I have 500 medium and hard leetcodes solved in the last year. Before I started grinding leetcode, I was terrible at leetcode (who would've thought). Same for Systems Design. I was terrible at it, got my ass handed to me in the first interviews it showed up. Okay, fine, go to the internet, find exercises, go through it. Learn the terms, the systems, the examples. Practice, practice, practice.

Nowadays, I pass leetcode and systems design interviews without a sweat. Behavioural interviews? Always the same shit, interviewers always want to hear the same boring story how magnificient you are but still humble and a team player. So you practice on 10 stories 100 behavioural interview question and focus on impact and teamplay. Takes a bit of time, but after that it's just choosing the right story at a given interview, easy.

Got an offer from Adobe which I rejected becasue they didn't offer full remote and got very far in the Google interview shortly before I stopped it, because they didn't offer full remote. Surprise, I'm now working full remote as a backend Software Engineer.

I have a ~50h week, of which is ~20h productive coding work, ~10h meetings, ~5h noise, ~15h for self-improvement, including leetcoding, design practice, APIs, frameworks, programming languages, general tech topics and whatever. Compensation could be higher (still, 75th percentile of salaries in my country), but I'm living well enough and can always join big tech later in life.

At the moment, I want to figure out if I can manage to build my own thing and life off of it. So, big tech can defintiely wait for another while.

What you can read out of that is; it's a grinding game. You suck at something, you start grinding it. Grinding means; do lots of exercises until you get good at it. You are stuck on a problem for 1+ hours? Look up the solution and understand it. Then a day later, you try again without the solution. Rinse and repeat until you are good. It costs a lot of time, especially at the beginning, but eventually, it gets easy.

People doing math and coding olympiads invest a lot of time into solving problems that prepare them well for those kinds of olympiads. There's prodigies, sure, but even they need to grind. If you don't want to invest the time to grind, that's fine, but there's no way around it. There's no shortcuts in life, especially if you're not born rich.

Re: Ask HN: Is programming a “young person's game”?

#32
Imo the quote “mathematics is a young man’s game” should better be read as “mathematics is a game for someone with ample spare time”.

As people grow older they have less time to devote themselves to singularly pursuing a goal (ie training for the olympiad). If you look at how people train for Olympiads, they spend an insane amount of time on it.

Re: Ask HN: Is programming a “young person's game”?

#36
Pushing 50 now and my output has only increased over the years (128 public repos on github, over half of them from the past decade).

I started playing guitar 8 years ago under a good teacher (couldn't even play a chord before that), and after a LOT of practice I can now play pieces like Capricho Arabe with deep feeling and skill that gets standing ovations.

It's not about when you start; it's about how much you put into it through regular, mindful practice (sometimes I'll put an hour into one basic technique or progression that involves 5 notes because it doesn't feel automatic and natural yet). Your brain doesn't harden as you age and lose its ability to learn new things; only your attitude towards new things tends to change (if you let it) because the familiar is comfortable. When you're young, you don't have as many familiar things to rest upon so there's more incentive to embark upon journeys of discovery.

Re: Ask HN: Is programming a “young person's game”?

#37
No. I got started late because I did other things and graduate school in other fields before starting. If anything, people who get started late are more likely to become good developers because they come in with existing experience in the world that makes them less likely to succumb to institutionalization, so to speak. What I mean by that is a huge amount of software sucks for no good reason other than that's the way it's done. So people who come to software from other fields than computer science and didn't start programming young can bring this new insight that asks "why?".

I learned Basic in junior high or something from the appendix from some VTech computer for like a week, and was like "ok, cool", and then left it alone.m and forgot about it. I didn't get my first job programming until I was 27 or 28 and had only programmed in Maple and Matlab for math courses before that. Maybe one shitty class in Java.

If anything, software is an old person's game, similar to architects and movie directors. You need a lot of experience to get to a top level. Programming and software, on the whole, isn't remotely close to olympiads or programming competitions.

Also, people's fascination with child prodigies is pretty ridiculous, in my opinion. Child prodigies are people that get to places faster but don't necessarily go further, in that other people catch up and even surpass. It's pretty rare that a child prodigy continues to outperform everyone else later in life, just like it is for anyone to outperform others. There are some, like Terrance Tao, who continue dominating, but I'm pretty sure he would have gotten there anyway without an accelerated childhood education, and he's rare enough that it's dumb to compare yourself to people like him.

Re: Ask HN: Is programming a “young person's game”?

#38
There are several things here in your views that I disagree a lot with.

First, you don't need to be a "kid prodigy" to be a great programmer. But even then, you don't need to be a great programmer at all as long as you're happy and do the things you like. In the end we'll all be dead, we might as well enjoy the ride.

Another note about the "kid prodigy" thing: just because someone wasn't a "kid prodigy" doesn't mean they were incapable to be a "kid prodigy". Prodigies aren't just hard work + intelligence, there's also opportunity, support, luck... I bet there's a lot of people out there that would have made excellent programmers but didn't have access to enough resources when they were growing up.

There's also a lot of bias in thinking that "great programmers" dropped down in skill after their 30s. They might not make headlines anymore but that's not correlated with skill. Linus Torvalds wrote Git when he was 36, for example. I'm sure that if you search for kernel contributors you'll also find "old" people there.

Another thing is that, as someone who has a degree both in computer science and mathematics, math and programming aren't really close at all. The thing that would be the closest one would be writing algorithms, but most algorithms you'll ever need are already written and implemented for you.

And now for the actual piece of advice: in every area of programming you will get better as you get older. There's so much about programming that comes from experience. I always tell juniors the same thing when I solve in two minutes a problem they've been struggling with: it's not that I'm smarter than you, I have just seen this problem or something similar already many times. You might want to find an area you like, and then keep on being curious, humble, and learning. That's what matters in programming.

Re: Ask HN: Is programming a “young person's game”?

#40
> You only see top programmers who started as kids and probably won some Olympiads and programming competitions

What does that even mean? What is a "top programmer"? I suppose those competitions are about clever algorithms (Olympiads) and assembly languages (demo scene, CTF,...)?

Or are there new contests I don't know about? Like "Best framework designer", "Best refactorer", or my favorite: "Best porter of old fortran code to Rust".

Post reply on HN