Jako Heiberg
HomeInsightsMusingsPortfolioAboutContact
Jako Heiberg

From DBase III+ to edge computing.
The journey continues.

Pages

  • About
  • Portfolio
  • Resume / CV
  • Insights
  • Musings
  • Archive
  • Contact

© 2026 Jako Heiberg · Cape Town, South Africa · UTC+2

Built with React + Cloudflare Workers. No PHP was harmed.

Back to Insights
Insights

The Long Game: Staying Employable Without Burning Out

A software career is a forty-year marathon disguised as a series of sprints. Here is how to keep learning without chasing every shiny thing, and keep going without burning to the ground.

August 19, 2026
6 min read
Technology

You have made it. You learned to code, built a portfolio, got past the interview, survived the first job, and become a real developer. This final post is about the part nobody frames as a skill: staying in the game, and staying well, for the long haul. Because a software career is not a sprint you win once. It is a marathon of decades, and how you run it matters as much as how fast you started.

Keep learning, but stop chasing every shiny thing

The field moves. Frameworks rise and fade, new tools arrive monthly, and the technology you are expert in today will be partly outdated in some years. Continuous learning is not optional in this career; a developer who stops learning slowly becomes unemployable, no matter how good they once were. That much is true and worth taking seriously.

But there is an equal and opposite trap, and it burns people out fast: trying to learn everything, chasing every new framework the internet gets excited about, feeling a stab of anxiety every time some tool you have never heard of trends. This is exhausting and, worse, unnecessary. Most shiny new things fade. Most hype does not last. You genuinely cannot learn everything, and the attempt is a treadmill with no end.

The way through is to invest most of your learning in fundamentals - how systems work, how to design software, how to debug, how to think clearly about problems - because those barely change and they transfer across every tool you will ever touch. Then learn specific technologies as you actually need them, driven by real work rather than by fear of missing out. A developer with rock-solid fundamentals picks up a new framework in weeks; the fundamentals are the leverage. Chase depth in the things that last, and let the churn of shiny things churn without you.

Specialise, generalise, or both

As your career grows you will feel a pull between going deep in one area and staying broad across many. Both are viable, and you do not have to decide forever right now. Specialists who know one domain deeply are valuable and often exceptionally well paid; generalists who can move across the whole system and connect the pieces are valuable in a different way and often make excellent leads and founders.

A pattern that serves many people well is to be broad enough to work across a system while going genuinely deep in one or two areas you love. You do not have to have this figured out at the start, and you are allowed to change your mind as you discover what you actually enjoy. The mistake is not picking wrong; it is agonising over the choice instead of doing good work and letting your real interests reveal themselves over time.

Relationships outlast any job

The developers with the best long careers are almost never the ones who sat in a corner and only wrote code. They are the ones who invested in people over the years - stayed in touch with colleagues, helped others without keeping score, built a genuine reputation as someone good to work with. Your professional network is not a LinkedIn number; it is the real human relationships you build across a career.

Those relationships are where your best future opportunities will quietly come from. The colleague you were generous to today is the person who recommends you for something wonderful five years from now, at a company you would never have found on a job board. Invest in people, sincerely and without an agenda, and it compounds in ways you cannot predict and cannot engineer. This is the quiet engine of long careers.

Find mentors, and become one

Early on, seek out people ahead of you who will share what they have learned - a good mentor can save you years of painful trial and error by pointing you around the potholes they already fell into. Do not be shy about learning from those with more experience; most people are genuinely glad to help someone earnest who is trying.

Then, as you grow, turn around and mentor those behind you. This is not pure altruism, though it is a good thing to do. Teaching forces you to understand things more deeply than doing ever did - you do not truly know something until you have had to explain it to someone who does not - and it builds your reputation and relationships at the same time. The developer who lifts others up is the one others want to work with, follow, and hire. Generosity is, among other things, a very long-term career strategy that happens to also make you a better person.

Guard against burnout like it is part of the job

Software has a burnout problem, and I will not soften it. The work can be intense, the hours can creep, the pressure can be relentless, and the always-connected culture makes it far too easy to let the job quietly consume everything else. Burnout is real, it is common, and it can take a genuinely long time to recover from - it is not a badge of honour or a sign of dedication.

Protecting yourself is not weakness; it is what makes a long career possible at all. Set boundaries and actually keep them. Rest properly - the myth of the developer who codes twenty hours a day and thrives is exactly that, a myth, and the reality is that a rested mind solves in an hour what an exhausted one flails at all day. Have a life and identity outside of code. Take real breaks. Sustainable beats heroic every single time; the person still going strong at forty is not the one who sprinted hardest at twenty-two and flamed out.

The long view

A career in software is one of the most rewarding paths available today - creative, well paid, flexible, endlessly interesting, and open to anyone willing to do the work regardless of where they started. It is also a long road with hard stretches, and how you travel it determines whether you are still enjoying it decades from now.

So keep learning, but from curiosity rather than fear. Invest in people. Guard your health and your life outside the screen. Do work you can be proud of, and be someone others are glad to work beside. Stay curious, stay kind, and stay in the game - because the developers who win the long game are not the ones who ran fastest at the start. They are the ones who were still running, and still happy to be running, long after everyone who sprinted had stopped.

You started this series wondering whether you could even do this. You can. Now go and build a career worth having. I am cheering for you.

Jako Heiberg

Software developer with 40+ years of building things that work. Full-stack, FastAPI, React. Based in Cape Town, working remotely, worldwide.

Related Posts

Insights

Vim From Scratch — Part 2: Modal Editing, and Why Modes Are a Feature

Every other editor lets you type text the moment you open it. Vim makes you ask for permission first. This sounds insane until you realise it's the reason Vim can do so much with so few keys.

August 26, 2026
5 min read
Insights

Your First Job: What Nobody Warns You About

You got in. Now everyone else seems to know things you do not, the real codebase is a horror, and you are convinced they will realise they made a mistake hiring you. Good news: all of that is completely normal.

August 12, 2026
6 min read
Insights

Surviving the Technical Interview

The technical interview tests a strange, artificial skill that barely resembles the actual job - which is exactly why you can prepare for it and get good at it. Here is how, without losing your mind.

August 3, 2026
6 min read