Choosing your career path

At some point in the career of a Developer they have to make a choice.

For some (including myself) it isn't a conscious decision, but rather something that happens by accident. It can be defined by the company you work for, your own interests, skillset or the skills of others that you work alongside. Either way, you make the choice or it is made for you. Both are fine, but its up to the individual to take control of that choice.

My Own Path

To explain this in more detail, I will speak mostly from my own experience.

Prior to my career as a Developer, I was more interested in design. When starting to learn coding, it was a means to an end to create well-designed user interfaces. I was not particularly interested in learning languages in great detail, but more in gaining just enough knowledge to create the ideas in my head. Through the course of my career, I've worked with multiple languages on frontend, backend and cloud projects, but my goal has always been the same: learn enough to do the thing I need to do. Prototyping ideas, developing solutions and architecting systems is where I find the most reward, which lends itself more naturally to a career as a Manager. This was something I discovered by accident, but this doesn't have to be the case.

The People vs. Project Dilemma

Ultimately, at some point in your career, the choice between people or project management will come up. The question is, do you want to focus on developing software or developing people?

For those who choose to develop software, the path often leads toward specialisation. Becoming an expert in a particular language, platform, or paradigm. You might find joy in deep diving into code, solving complex technical challenges, and becoming the go-to person for tough problems. You'll likely still collaborate, mentor, and influence, but your core value is your technical skillset and how you apply it.

On the other hand, if you find yourself more drawn to team dynamics, planning, and helping others succeed, then people management may be the more fulfilling route. It doesn't mean leaving tech behind, it means using your technical experience to guide and support others. Success becomes less about what you build, and more about what your team achieves.

Shaping Your Own Direction

Neither path is more valuable than the other. What matters is aligning your work with what energises you. That might mean stepping away from code entirely, or doubling down on it. It might mean becoming a tech lead, a mentor, an architect, a Head of Engineering, or none of those.

The key is not to let the choice happen in the background. Reflect, ask questions, and try things. Talk to people in roles that interest you. Ask for responsibilities that stretch you in the direction you're curious about. You don't need to have it all figured out, but you do owe it to yourself to explore intentionally.

Because whether you write code or lead people, your career is something you get to shape.