Live data from Hacker News

Aging programmer

world.hey.com

11–20 of 375 posts

Re: Aging programmer

#11
>I never understood why some people despise the term full-stack.

More for the role: full-stack has you doing multiple roles, but is not compensated as such. You're even removing the communication overhead if the role had been split in two. It seems to me as a business move to compress roles and pay you less for double the capability in exchange for varied work. I don't think people should just accept lower comp just because they prefer varied work.

Re: Aging programmer

#12
post #2

Here’s something I think a lot of people don’t think on: 40 years old is mid-career. If you expect to retire at 60 (likely 65 these days) and you start working at 20: 40 is smack dab in the middle of your career. I think that notion gets lost when we talk about ageism in tech and then people talk about 40-somethings.

40s or 50s are still prime time for programmers, assuming he/she keeps learning and coding and designing. but those are still of small group, it's like a normal distribution, I read somewhere age wise there are only about 1.5% that are above 50s.

I'm better now than I ever have been. I was trash in my Jr years. Being discriminated against due to age would be a grievous error on the part of any potential employer.

Re: Aging programmer

#13
post #10

I wonder where the genesis is of this idea that programming is young person's game akin to physical sports where speed, explosiveness and endurance matter. It seems to me that it's an intellectual activity where one should go on for very long honing their skills and becoming better and better at it with age. Maybe the industry sidelines the older more experienced technical folks at a cost, and that's why there seems…

Younger people with cognitive bias running the hiring shit show perhaps?

Re: Aging programmer

#14
post #2

Here’s something I think a lot of people don’t think on: 40 years old is mid-career. If you expect to retire at 60 (likely 65 these days) and you start working at 20: 40 is smack dab in the middle of your career. I think that notion gets lost when we talk about ageism in tech and then people talk about 40-somethings.

A lot of programmers who are 35+ can struggle to find further opportunities as the more senior you are the less available those opportunities are and the more expensive you are. Lots of companies only want young people who are naive and have limited distractions outside of work. So, really, programming as a field is front loaded and the longer you stay in the business over 35 then the luckier you have been. But make sure you have an effective exit strategy to support yourself and your family when the boss doesn't like folk older than him.

Re: Aging programmer

#15
post #9
post #7

Earlier quoted context omitted.

Limiting a software engineers career to less than 20 years is a pretty fucking idiotic thing to do.

Sure. Ageism, sexism, racism, etc, etc, etc, are all fucking idiotic. And yet surprisingly popular. So we have to deal with them.

I agree with you, but imagine being a discriminatory, but rational asshole.

Of course you're not going to hire a woman if you could hire a man - they might get pregnant and be away from work for a long time.

Of course you're not going hire an older employee that knows their worth over a recent graduate that isn't familiar with the salary they should earn. You can rip them off much more easily.

People can be cunts but still act with some rational motivation. That's why we have protected categories, to make sure that that isn't a strategy worth pursuing.

Re: Aging programmer

#16
post #10

I wonder where the genesis is of this idea that programming is young person's game akin to physical sports where speed, explosiveness and endurance matter. It seems to me that it's an intellectual activity where one should go on for very long honing their skills and becoming better and better at it with age. Maybe the industry sidelines the older more experienced technical folks at a cost, and that's why there seems…

Maybe because a 25 year old can work 12 hours a day, while a 40 year old often has family obligations that make that impossible.

Re: Aging programmer

#17
post #6

Add 13 years, and I could have written this. I must admit I cringed a bit when the author said 40 was old. I still love what I do, and I have no desire to live the manager life of all day meetings.

If you can be the best NFL Quarterback at 45 I think you still have a shot at writing code at 40.

Re: Aging programmer

#18
I learned how to code when I was twelve. I wouldn't have if I didn't in some degree enjoy the actual act of coding, the moment to moment typing on the keyboard, composing algorithms, designing data structures and logical flows. But in the back of my mind I also always regarded coding as a means to an end. Sure I became engaged in language design battles, API design philosophy, but the magic with computers was always, for me, that you could create something from nothing, this totally metaphysical creativity, really. To some extent I see this passion transgressing to other spheres, such as management, communication, planning across departments, office politics. As an adult, I don't play video games, and artistic pursuits and ideals have also become more abstract, the particularities more sedimented, incorporated in the grand scheme of Life. On top of that, the fact is that most programming jobs are glorified plumbing. I'm reconciling with the fact that the romantic days of hacking are perhaps a thing of my passed. I don't really listen to music the way I did as a teenager, so I can't expect programming to remain the same either.

Re: Aging programmer

#19
post #10

I wonder where the genesis is of this idea that programming is young person's game akin to physical sports where speed, explosiveness and endurance matter. It seems to me that it's an intellectual activity where one should go on for very long honing their skills and becoming better and better at it with age. Maybe the industry sidelines the older more experienced technical folks at a cost, and that's why there seems…

In my mind, young male have a lot of hormones that make them compete and it shows. There seems to be clear behavioral change in the average programmer as they age. Later in life (oftentimes with family), they do not have biological set-up to code 14 hours a day whole year as they did before.

Obviously, outcoding everybody else is sometimes considered as a value and other times it is not. Shrug.

Re: Aging programmer

#20
post #6

Add 13 years, and I could have written this. I must admit I cringed a bit when the author said 40 was old. I still love what I do, and I have no desire to live the manager life of all day meetings.

I’m approaching my 40s and I am not really worried. On the contrary I feel confident on my tasks. Author is cringe just like his masters at Basecamp.
Post reply on HN