Live data from Hacker News

Is software development really a dead-end job after age 35-40?

quora.com

41–50 of 411 posts

Re: Is software development really a dead-end job after age 35-40?

#41

Earlier quoted context omitted.

I also think a good manager can double or quadruple the effectiveness of their entire team Another way of thinking about this: Managing people really well is really hard. Most managers are not the best managers. Average managers often end up doing things that reduce the output of their group in the interest of things not going horribly wrong. The Pareto distribution rears its ugly head, once again.

I wish I had more than one upvote. If you have no management experience, and no mentorship in managing, you have no business managing people. Managing requires empathy and a desire to help your subordinates level up, not SWE skills. Your job is to deliver value to the org and to your individual contributors in equal parts. At least as a software developer, you're only breaking code. But you start affecting people's l…

How about team lead?

Re: Is software development really a dead-end job after age 35-40?

#43
I'm frankly flabbergasted why silicon valley (apparently, from reading articles here) has this youth fixation. In my software dev experience the least useful people on the team have invariably been the youngest. My pet theory answer for my own question goes thusly: Young people are more easily indoctrinated / brainwashed and dominated and thats what Google and whoever really want in their employees.

Re: Is software development really a dead-end job after age 35-40?

#45
post #41

Earlier quoted context omitted.

I wish I had more than one upvote. If you have no management experience, and no mentorship in managing, you have no business managing people. Managing requires empathy and a desire to help your subordinates level up, not SWE skills. Your job is to deliver value to the org and to your individual contributors in equal parts. At least as a software developer, you're only breaking code. But you start affecting people's l…

How about team lead?

Team lead is acceptable as it's more of a servant leadership relationship, and under the right circumstances, a team lead should be able to grow into a full blown manager role.

Re: Is software development really a dead-end job after age 35-40?

#46
post #31

This is depressing. I'm 33 and still haven't really find a niche inside software dev that I'm willing to stay... On the other hand, nobody asks doctors and lawyers if their are planning to retire at 35.

I'm 37 and would rather not stick to a niche personally. Being able to quickly adapt and grow keeps the job interesting to me.

Re: Is software development really a dead-end job after age 35-40?

#47

I'm frankly flabbergasted why silicon valley (apparently, from reading articles here) has this youth fixation. In my software dev experience the least useful people on the team have invariably been the youngest. My pet theory answer for my own question goes thusly: Young people are more easily indoctrinated / brainwashed and dominated and thats what Google and whoever really want in their employees.

[deleted]

Re: Is software development really a dead-end job after age 35-40?

#48

In the general sense, this is the wrong place to ask. It's a self-selecting group in that most people over 40 here will be among the group that lasted in the career. It won't give a sense of how large that group is in the wider world, nor how many didn't stick with it. On the other hand, if you want to hear how to make it past 40 in software, this is probably an excellent place to ask!

Then let me ask: how do you make it past 40 in software? Specifically, how do you position yourself so that you are actively sought after (rather than merely employable)?

Find a niche that rewards experience in something other than code. This could be non-technical (e.g. "business"), or it could be something more deeply technical (e.g. scaling, machine learning, search, etc.) To some extent, the older you get, the more this happens, naturally. But you can and should make strategic decisions about where you choose to devote your attention.

The important principle is that you should devote your learning time to things that are more likely to survive. A good way to do this is to pick something that has been around for a long time. Knowing how to write an optimized linux kernel driver is far more long-term-valuable than, say, a Javascript framework. Knowing how to do quantitative marketing is even more valuable than that.

The absolute worst thing you can do is to chase the new shiny every year. If you do that, you will never be more experienced than the most junior member of your team.

Re: Is software development really a dead-end job after age 35-40?

#49

In the general sense, this is the wrong place to ask. It's a self-selecting group in that most people over 40 here will be among the group that lasted in the career. It won't give a sense of how large that group is in the wider world, nor how many didn't stick with it. On the other hand, if you want to hear how to make it past 40 in software, this is probably an excellent place to ask!

Then let me ask: how do you make it past 40 in software? Specifically, how do you position yourself so that you are actively sought after (rather than merely employable)?

Java and Spring, or C# and .net. Java is derided as the next cobol, but there is a lot of new development, lots of jobs, and strong demand for senior talent. Source; me, been doing java since 2003. Age 40+.

Re: Is software development really a dead-end job after age 35-40?

#50
post #34

Sitting in an office 9-5 is dead-end job. Most people move into independent consulting, remote work, their own business....

Sitting in the office, undisturbed, for eight hours, coding - sound perfect to me!

If you are in an office, and also undisturbed for 8 hours, that tells me you are not in a 9 to 5 job.
Post reply on HN