Ask HN: How many are 30+ years and still active programmers?
How many of you out there are still active programmers contributing to open source and community, while being greater than 30 years ? How to you manage personal life, work and contributions ?
84 comments
[ 0.17 ms ] story [ 174 ms ] threadAre you afraid that programming skills deteriorate with age for some reason?
I think if you try to be excellent at what you do and improve over time, there is no reason you should have to worry about this until your brain is actually withering away.
> I think if you try to be excellent at what you do and improve over time, there is no reason you should have to worry about this until your brain is actually withering away.
It sounds like a pretty serious problem to me. Everybody knows the meme, so when they're hiring older people they're really going to try to rake them over the coals in the interview to make sure they don't hire one of those 'old people stuck in old technologies; can't code' devs. This makes it much harder for those who can still code to pass technical interviews.
It's more like Civilization, where you spend more time looking at the board and thinking of moves than you do actually entering moves. And the more times you play, the more problems you've encountered, and the more possible moves you see. The Huns are attempting to flank you? Been there, done that. Someone picked up a wonder? You can work around that. Playing against Ghandi? Look out for them nukes.
And if you decide to play co-op Civilization with a newbie, you have the opportunity to help them bypass some of that learning curve, by passing on the things you have learned over your years of play.
The advantage of having seen all of the problems, in business terms? You don't have to spend a lot of time figuring out how to solve them, and you won't make a lot of mistakes while solving them. You can get past these simple problems in no time flat, and move on to the problems you haven't seen before. This makes you fast at 90% of the tasks you face.
The downside of having seen all the problems? You have a solution that you know works for every problem, and might not see the benefit in trying other solutions. When the Huns flank you, you send 50 spearman units to break the flank. But what about 10 artillery units? Or 1 tank?
When you know a solution works, you have to consciously push yourself to try a new solution. For some people that's easy, for others, not so much. But if you really want to remain at the top of your game, you need to make that push.
Programming wise and learning wise i've also grown wiser and know where to have my focus to be able to get better, faster and learn new technologies with my own mental algorithm. Though this most likely has nothing todo with being over 30, but maybe more with the time and experience gained over time. But as you get into the 30s, some people get kids and buy a house and what not. But that will also in time teach you how to manage the time you have available, and you will try to work more efficient and narrow your focus onto your goals and tasks in your everyday programming job or what you're doing, you learn to filter away all the noise and stay focused on the task at hand.
I got a late start in the field (studied physics in college and graduated in to the 2008 recession) and suspect if I'd been just a year or two later I'd have never made it happen.
If that is the case then you just need to grab time as and when you can. You will find you can find half an hour a day at least. The limited time will help you focus. I find I get up early or stay up late to make time for this.
Started at 12yo too... I've written a lot of code, and will continue to add to the pile until they pry my keyboard from my dead, cold fingers!
In a little over 2 weeks I turn 32. I don't see or feel like retiring in 3 years.
For me programming is akin to a work of art, so i keep doing various projects for my own fun.
Not sure how one can become "inactive", barring a disabling accident.
Still going strong.
I also run weekly data analysis workshops with my staff, where I get to teach junior analysts and engineers how to think Bayesian, and how to replace Excel with Pandas.
Having the time of my life at work :)
Get some nice chunks of free time by contracting and taking chunks of time inbetween, though I guess this could change once kids come into the story.
I'm much happier like this.
Really looking forwards to it.
When I work on personal projects, I contribute to open-source when I find something to fix in the libraries I am using. But that's just a side effect, not a decision to do extra open-source work in my free time.
I've done a little open source but mostly shy away because I just want to code, not get into meta-arguments over style or whatnot. Not saying every project has that issue specifically, but I don't have time to sift through and find "compatible" communities to contribute to that are also doing projects I find interesting.
It's my 12s anniversary as a professional programmer. Did work on all kinds of projects: a hugely popular online game, a search engine, all kinds of smaller projects. Love programming more than ever.
Couple of noticeable age-related factors:
1. As a proud father I have to be very careful when planning my spare time. For example, I mostly do hobby projects early in the morning now.
2. Got my first serious RSI-related trauma recently. Younger programmers, please, start caring about your hands as early as possible!
How?
Standard laptop keyboards and mice are a crime against one's hands, it's generally better to replace 'em with something ergonomic.
I did boxing as a university sport. That was the worst choice possible: I developed early-stage osteoarthritis.
2. Posture/ergonomics
3. Take frequent breaks while coding.
4. do minimal typing when you are not actively coding.
[0] https://www.youtube.com/watch?v=cD8BGa3p1Ms