DEV Community

Ben Halpern
Ben Halpern Subscriber

Posted on

What's your advice to someone over the age of 30 considering a career in software development?

Top comments (80)

Collapse
 
amypellegrini profile image
Amy Pellegrini • Edited

Pick a marketable stack to learn

Software Development is an incredible vast discipline and there is literally no limit to what you can learn/do with it, but first and foremost you want to make sure your skills are put to use in the market so you can sustain yourself. Nowadays there are plenty of learning resources which will teach you precisely what you need to know to join the workforce (JavaScript, React, HTML, CSS should be a good start, Git is a must).

Don't get spooked by gatekeepers

There will be people who will tell you "it's too late/you can't do it/too difficult/etc". Don't get spooked by such statements, you may not be able to land a Senior position or cherry pick your salary, but if you can solve problems, communicate well, and demonstrate your ability to learn, there are plenty of businesses that can benefit from your work. Remember that software development is ultimately about implementing solutions that other people can benefit from using code as a medium. If you can help other people, they will help you, even if you are not the best programmer in the world.

Put you prior experience in perspective

The ability to communicate, research, negotiate, particularly if you can lead other people, can be a great leverage to trigger your career. If you are used to solve difficult problems, be accountable, "owning your mission" as they say, this can be a great asset for a potential employer. From an employer's perspective, what matters is how much value can you provide for them, not so much how a good developer you are. I know this will infuriate some people but is a hard fact about the reality of the world which doesn't mean you can't get better over time provided with the right opportunity.

Get used to uncertainty

Tech keeps changing all the time, that's why I don't believe the people who say that you can't do it unless you start young. New stuff is developed all the time and there are no rules on how it can be used. If you embark in this journey you will have to keep learning and updating your skills forever, so don't assume that knowing any given stack is assurance of anything.

Create a nice showcase

The best way to learn to code is by coding, and no code is good enough unless it solves some actual problem in the real world. If you develop a useful piece of software and release it to the world, there is no better presentation card than that, even if there is something similar already there. You can do your own version of some tool with some variation or adjustment according to your personal taste or use. There is enough people in the world to guarantee that somebody will prefer your version of the tool over some other version of the same tool.

Learn from the best

You can save a lot of time and learn very fast by following the right people and investing in the right resources. You just need a Twitter account to find really amazing people from whom you can learn a lot and keep yourself aware of tech trends (I do this!). Many of them will be very happy to answer your questions and give tremendously useful advice for free. If you know someone in the industry willing to guide you or provide some mentoring, that can be of great help. If you start networking with those people you can speed up your learning a lot. Once you find the right people, you'll see most of them can provide high quality education by a fraction of the price that you would pay from traditional sources.

Be humble

Remember that some of the smartest and most intelligent people in the world are working as software developers, and you'll only gain their respect by being humble and knowing you own position in the industry. There is no shame in ignorance as every person in this world is born ignorant, so don't be afraid to ask questions and make your presence be noted in forums which are dedicated precisely to people like you. Rudeness and egotism are not appreciated in this craft, spite some popular characters which may present themselves in that fashion. Avoid the toxic people, the gatekeepers, and anyone who tells you you don't belong here.

Hope it helps!

Collapse
 
emilper profile image
Emil Perhinschi

agree with all the points, only need to add this:

  • Don't quit your former job while you're still learning, you might discover that while you're good at writing software you hate to do it 8 hours a day, 5 days a week.

  • Software writing is not a career, it's a vocation. You'll never stop learning, the years of experience won't be a guarantee for finding employment, and after you get to "senior" there will be very little opportunities for formal promotions.

Collapse
 
tedhagos profile image
Ted Hagos

"and after you get to "senior" there will be very little opportunities for formal promotions" . - that

Collapse
 
amypellegrini profile image
Amy Pellegrini

Indeed! Thanks, you are right on point, I'll add these points to my original post if that's ok

Thread Thread
 
emilper profile image
Emil Perhinschi

sure, feel free to add them :)

Collapse
 
kenovienadu profile image
Ovienadu Ken

I totally agree with you in every way. Sometimes it's very easy for people(gatekeepers) to drop discouraging comments like software development is difficult and only for geniuses. I may be new in software development as well but one thing I have come to understand is that software development is for everyone. Developers constantly learn and improve on their previous knowledge. So don't give up. Besides, age is just a number. As long as you're willing to learn, you can make a great developer. Everyone is learning one new technology or the other. 💪🏾💪🏾💪🏾

Collapse
 
tamouse profile image
Tamara Temple

Turn this into a post, it's that good, or better :)

Collapse
 
amypellegrini profile image
Amy Pellegrini

Thank you! Yes, I'll most likely turn it into a post and add some edits/suggestions by some people here (I'll make sure to give proper credits)

Collapse
 
mtallerico1 profile image
Mike Tallerico

Wow! Awesome. Thank you for this.

Collapse
 
jamonjamon profile image
Jaimie Carter

Great advice. Thanks.

Collapse
 
ben profile image
Ben Halpern

Amazing

Collapse
 
naijadeveloper profile image
naijadeveloper

thanks

Collapse
 
bvmcode profile image
bvmcode • Edited

I started in my mid to late 30’s. I was an 8 year employee at a Fortune 250 when I decided to completely change my career direction. They completely supported me. So I understand that a lot of people don't have that luxury. But it wasn't easy, still not easy. Imposter syndrome is amplified and you always feel in catch up mode. Sometimes you feel you aren’t taken seriously. So you need to find a way to overcome those things. It’s hard to give advice there because I struggle with it constantly. The advice I do have is

  • constantly build things
  • Be proud of the wins, big or small
  • Don’t get consumed by the struggles
  • It’s ok to use google
  • Have a mentor, or two
  • Don’t feel you need to know EVERYTHING
  • And you have a family make sure your side projects doesn’t conflict with the time your family needs. Some things are more important than programming.

EDIT - what people are saying about previous experience is spot on. For example, I had tons of Excel and analysis experience before my career switch. The mode of thinking in terms of setting rules and logic transferred nicely.

Collapse
 
_hs_ profile image
HS

"Don’t feel you need to know EVERYTHING" - wish I knew this back when I started working for clients fresh from university. Sometimes I still need someone to tell me to pull the break and "just make it work". :D

Collapse
 
nanythery profile image
Nadine M. Thêry

Thank you, I needed to read something like this, hehe.

Collapse
 
azza85 profile image
aaron

This is a good article about not knowing everything from Dan Abramov. overreacted.io/things-i-dont-know-...

Collapse
 
aspittel profile image
Ali Spittel

Don't discount your previous experience. Use it. If you're career changing from insurance to coding, for example, you have the industry context of insurance and if you can find a programming job in that industry you have a huge advantage because you can merge those two worlds super well.

Collapse
 
databasesponge profile image
MetaDave 🇪🇺

Yes this is huge, and I'll venture to say that it's not just what do you know professionally, but what do you also do outside of work?

A keen hobbyist, a mother of four children, a person who loves fitness training ... they will probably all have a very great perspective on what they want out of technology, and what others like them would want.

Collapse
 
remotesynth profile image
Brian Rinaldi

@ali Spittel said exactly what I wanted to say exactly how I would have wanted to say it. 🙌

Collapse
 
mortoray profile image
edA‑qa mort‑ora‑y

This question makes me feel old!

I'd say the same thing I say to anybody asking about and kind of career switch, "Do it."

You've got only one life. Sure, you'll encounter all sorts of hurdles in your quest. It may turn out not to be the right thing for you -- programming is not for everybody. Stay flexible the entire time. You never know what aspect you'll find enjoyable and where you end up.

Collapse
 
veebuv profile image
Vaibhav Namburi

Your past experience will be your biggest asset. EQ > IQ. Use that and combine it with excellent programming skills and you'll move at lightning speed in a matter of 2 years. Also, join a 10 person start up, not to big and not too small.

Big enough for stability, small enough to leave a massive impact

Collapse
 
maheshkale profile image
Mahesh K • Edited

Let me put some realistic advice. Don't think of it as a gatekeeper point of view but more of realistic view on where to put your head. The answer is not intended as shot of ageism but if you want to take your anger and vent at me. So be it. Still I wish to stay realistic.

  1. Degree does matter, when you are developing serious applications. e.g. With arts and humanities degree, if companies start to hire the intern grad for the rover or the drone programming where even small change in float value can destroy a product, that's where the degree comes in for in depth involvement of developer or worker. Don't think of this as a gatekeeper point of view, this sort of products are in realistic world, with realistic expectations. If companies start to compromise on who they hire, that reflects in final product. We can't do kumbaya, lovey dovey in this sort of sector especially when recession kicks in.

  2. Age does matter. You can play around Javascript, CSS and HTML. And you can take yourself upto age of 70 if you have less memory loss issues. However trying to build applications that involve lot of calculations (say finance sector) and testing means your age matters for attention of details and execution towards it. As we age we can delegate better but we are also likely to miss out on small details, which matter a lot, when we learn new stuff and also try to execute it.

  3. Salary does matter. If you are going to be into Web dev position salary is not going to be 120k plus unless adobe or top 100 MNCs hire you. That's where the maintenance projects come in. So let's say you learn to code, try to find maintenance projects where you are fixing someone else's code or product instead of building from scratch. Those jobs do pay and many MNCs are always in search to find a guy in such case.

Lot of people here don't tell you the reality.

  1. Try writing React like framework from scratch in 50s, you'd exhaust. Try remembering workflow for making dashboards using your full stack knowledge in 50s. It's even more harder. Being under 40 would be lot more ideal time for this. Sure exceptions exist but they are exceptions for a reason and not the norm.

  2. Try to remember which library is right for the job as you age, that decision making switch is even more harder.

  3. Try making game that involves a lot of complex details, you'd exhaust making games too.

  4. Work life balance is harder upto 40, and after 40, even health comes into equation.

  5. Religious, political and social opinions also have impact considering IT and Dev field is more of left leaning, you will definitely face lot of forced opinions on you in such context.

Note: Remember that programming, gaming, video streaming and vlogging are extremely exhaustive activities, where your age would definitely impact the performance. Will power can get you ahead but there is also limit to how much body can take.

However,

If you want to build your career in say Web Development I think there are less obstacles and nobody should stop you from getting into it. HTML, CSS and Javascript is easy to learn and retain in head for decades. It should not stop you from getting that junior dev job and move upwards from there.

So my suggestion: Go for jobs like say - Web Dev, WordPress support specialist, theme and plugin development for web based app or product, front end web dev, designer etc.

Collapse
 
jamonjamon profile image
Jaimie Carter • Edited

Buddy, I'm 50. I apologise in advance for the directness of this reply, but since we're speaking honestly here: I work in a much higher pressure complex technical situation than you ever will. Every day. There's a reason I get flown all over the world (which I hate) to do the jobs that affect millions of people. Why? Because I'm 50. Nobody younger can handle the pressure or has the experience I have, or believe me they wouldn't be paying me what they are - they'd have someone younger for less $. I'm sorry and hope I've not offended you, but you really need to have a good think before saying this stuff. I suppose, I used to have the same view at your age... It's just not an accurate view point. Oh, and I went to University and did 1st year engineering... It's ok. I can add up.

Collapse
 
maheshkale profile image
Mahesh K

No offense taken. I can understand you point of view. My point regarding the 50s wasn't meant to be ageist but more of realistic view of how some people here were not realistic about starting something from scratch in this age bracket. Again this is based on what I have seen from the people who are restarting the career at that age bracket on those specific tasks. Again not meant to say that innovators, entrepreneurs, coders don't exist on 50s, 60s, and onwards. It's just people are not being honest about age bracket and physical limitation.

Thread Thread
 
jamonjamon profile image
Jaimie Carter

That's good you're not offended, though you did miss the point. That's ok, it'll click later on down the track.
Just out of interest, you sound like you have experience in high stakes projects. Do you lead a team (sorry, I don't know the correct terminology) or are you part of a team working on a big project?

Thread Thread
 
maheshkale profile image
Mahesh K

Yes, working with one team on project for govt.

Thread Thread
 
jamonjamon profile image
Jaimie Carter

Ah. Very cool. I have a friend that has a few govt contracts in the local govt management sector. Which area are you developing for?

Thread Thread
 
maheshkale profile image
Mahesh K

Energy & infrastructure sector.

Collapse
 
adamphilbin profile image
Adam Philbin

Sorry, I had to sign up after a long time lurking just to reply to this - ageism aside, this is completely incorrect from my experience. The older, more experienced developers I know (I sit somewhere in the middle of the age spectrum myself) are typically the most detail oriented, having already learnt the cost of half-assing it.

I don't want to be negative about any other group, so I won't go down the road of "if anyone's likely to be sloppy and ignore the details, it's XYZ...", but what I've witnessed in my career (even if anecdotally) is completely contradictory to your post.

Collapse
 
ceceliacreates profile image
Cecelia Martinez

I'm 32 and just now getting into development. However, I have known HTML/CSS for more than a decade and have worked on tech-related projects in other fields, and have leveraged that as much as possible when talking to recruiters. Leverage anything technical you possibly can.

Networking like crazy is super important, because it lets you present yourself and pitch yourself in a way your resume might not. People skills and communication skills are more important than you think. Actively doing things that represent your skills (projects! volunteering! writing!) show that you can still learn and are actively doing that in a self-directed way.

Ultimately, I'd recommend NOT going into software development after 30 unless you REALLY want to be a software developer and are passionate about programming. It's going to be hard. If you're just in it for the money, there are probably easier ways to leverage your experience (or go into sales if you're a people person).

Collapse
 
sally profile image
Sally

"Ultimately, I'd recommend NOT going into software development after 30 unless you REALLY want to be a software developer"

  1. Why not?
  2. Why would someone go into software development and not really want to be a software developer? That seems like a poor move at any age.
Collapse
 
ceceliacreates profile image
Cecelia Martinez

There are some people that get into it because they hear you can make six figures without a degree/etc. I agree it's definitely a poor move at any age, it just tends to be more associated with those switching industries mid-career.

Thread Thread
 
sally profile image
Sally

I like to say being a software dev is like being a professional sportsperson. You need to enjoy it; there has to be a passion there. It would be unusual to be hired if you were only 'in it for money' yet lacking skill and passion. If you somehow manage to get hired despite hating every second of it, you'll burn out fast. Tech by its very nature - a bit boring, lots of sitting, frequent frustrations - will filter out those that hate it or are indifferent to it early on.

Thread Thread
 
ceceliacreates profile image
Cecelia Martinez

Definitely agree! My advice would be more for those on the fence because they heard it's good money but don't really like it, before they pay for a boot camp or other courses.

Collapse
 
martyhimmel profile image
Martin Himmel

Transferable skills are a real thing and can give you a view that others may not have. Be creative with your previous experience and explore/demonstrate what you've learned and how it can apply to development.

I did exactly this. Was a dental tech until I was 32, then switched careers. Previous lab management experience helps me see more than just code - business needs, customer needs, training other employees, etc.

Collapse
 
ben profile image
Ben Halpern

I've offered similar advice to others.

  1. Learning to code is something anyone can do if they find the activity at all engaging. (Even if you have to get over some humps before it clicks)

Then it becomes finding your place in the market as a hireable coder.

Position yourself as different from other "junior dev" candidates as someone with a decade in the workforce who is going to understand the dynamics of professional collaboration and will provide way more value than a comparably experienced software developer.

Collapse
 
peterwitham profile image
Peter Witham

This is such a great question.

  1. Do it.
  2. Pick a few different things that you are interested in and try them all to find the one that feels like home, then commit to it.
  3. Do not listen to the naysayers, listen to the folks here on dev.to to stay motivated and driven.
  4. Find a community locally if you can and attend regularly, I wish I had done that when I was starting out more.
  5. In the words of Mr. Churchill, Never Give Up.
  6. Accept that somethings will come easy and others will be a hard-fought battle with great rewards when you solve the problem.
  7. Accept that whatever you decide to focus down on will probably change or even get replaced, do not let that distract you. Every technology has a place out there for someone. There are those with fantastic careers supporting old technologies because they will always be needed.
  8. Do not compare yourself to others, compare your progression to last week, last month, last year.

Just a few thoughts.

Collapse
 
niorad profile image
Antonio Radovcic • Edited

30 is not old. If you spend your 20s in academia, bachelor's, master's, maybe PHD, you're almost 30 when you start working.

We hired folks who transferred from other occupations to development. It's not unlike other areas; you have to learn the basics on your own.

It may take a year, depending on your available time, to educate yourself to a level where you can get an internship or junior-position.

Once you have a foot in the door, it gets simpler. You can learn and get experience on the job from now on.