This question was recently discussed in a Belarusian IT publication. The original article asked whether it was possible to become a programmer after the age of 40. The author, whose series initially began as a story about transitioning from journalism to software development, eventually turned it into a collection of beginner PHP lessons and drifted quite far from the original topic. Judging by the articles, however, it seemed that he never actually managed to leave journalism behind and become a programmer. That leaves the impression that becoming a software developer after 40 is possible—but far from easy. So let’s lower the bar a little and ask a slightly different question: what about after 30 or 35?
This topic feels very personal to me because I currently earn my living as a journalist while dreaming of becoming a professional software developer myself. Despite my age. Given today’s IT labor market and the ongoing shortage of qualified developers, more and more people are talking about retraining professionals from other industries. So I wouldn’t hesitate to say that this is a topic of broader social importance. If you’re interested in exploring this question together, read on.
I’d also like to point out that my desire to become a programmer isn’t based on the cliché of “developers make a fortune, so I want that too.” It’s a conscious decision. Deep down, I’ve considered myself a programmer for many years. Programming simply hasn’t become my primary profession yet. I hope—perhaps naively—that most people who decide to switch to software development later in life are motivated not just by salaries but by self-fulfillment and similar personal values.
So what are the advantages of becoming a programmer?
The Advantages
The obvious ones
- Self-fulfillment. If someone hasn’t found satisfaction in their current career, there’s a chance—though certainly not a guarantee—that programming could become the field where they finally enjoy what they do. Of course, this raises another question: why weren’t they able to enjoy their previous work, and are they capable of enjoying any job at all? That’s a much broader discussion, so let’s leave it outside the scope of this article.
- High income. This one hardly needs explanation. According to virtually every salary survey, the IT industry offers some of the highest-paying jobs available. This isn’t true only in the former Soviet countries but across much of the world. And there are good reasons to believe this situation won’t change dramatically anytime soon.
The less obvious ones
- Flexible working conditions. Software developers and web designers can often work remotely or maintain flexible schedules—something many other professions simply don’t offer.
- The opportunity to move abroad. Developers from our region are highly valued internationally. The same cannot always be said for accountants, economists, or lawyers whose qualifications may not transfer easily to other countries. For those dreaming of building a life elsewhere, a career in IT can open that door.
These are the factors that make people seriously consider becoming programmers. But, of course, it isn’t nearly as simple as it sounds. Otherwise, everyone would have quit their jobs long ago and started writing code—and there certainly wouldn’t be a shortage of developers today.
So What’s the Problem?
Changing careers as an adult isn’t easy.
When we’re choosing a profession at 17 or 18, most of us have only a vague idea of what our future job will actually look like. Parents, friends, social expectations, or even trends often influence our decisions. (In the 1990s, for example, economics was considered a prestigious degree, which explains today’s oversupply of economists.)
As we grow older, we gain a much better understanding of ourselves—our interests, strengths, and ambitions. Sometimes that also means realizing that our current profession has become painfully boring. A 17-year-old usually doesn’t face this problem, but they have one enormous advantage: youth.
Once you’ve reached your thirties or beyond, changing careers becomes a much more intimidating prospect. Your intuition tells you there will be obstacles. And when it comes to becoming a programmer after 30, those obstacles are usually the following.
- Family responsibilities. By the age of 30 or 35, many people have spouses, children, or financial commitments. Taking risks becomes much harder because you’re no longer responsible only for yourself. There’s no guarantee that your new profession will immediately provide the same level of income. You may have to accept a temporary pay cut while gaining experience.
- Employers expect juniors to be young. Hiring managers often picture a junior developer as a university student or recent graduate—not a bearded professional in his thirties or forties who looks more suited to managing a team than writing entry-level code. Even if his technical skills are at a junior level, his age can work against him.
- Starting over isn’t easy. Not everyone is ready to become a student again. By the time people reach their thirties, they’ve usually established themselves in another profession. They’re used to being seen as experts and often find it psychologically difficult to admit—even to themselves—“I don’t know this.” Learning becomes emotionally harder. I won’t include the common argument that “your brain isn’t what it used to be.” If someone has kept their mind active, a 35-year-old brain is still perfectly capable of mastering complex subjects—and often outperforms much younger people. Programming itself demands exactly that kind of active thinking.
- Fear of not fitting in. This point overlaps with the previous ones but deserves separate mention. Personally, it’s probably my biggest concern. It won’t be easy to accept that I’ll be surrounded by colleagues much younger than me who know just as much—or more. And if I have to deal with the occasional joke or skepticism directed at “the bearded guy who decided to become a programmer,” that could make the transition even more difficult.
- Fear of disappointment. What if, after all the effort, the new profession eventually becomes just as routine and uninspiring as the previous one? That’s another thought that often prevents people over 30 from taking the leap.
I’d be very interested to hear what the community thinks. Is it realistically possible to become a software developer after the age of 30 or 35?
This is machine-translated content. Original article in Russian: https://habr.com/ru/articles/204168/