The Question That Changes Everything (But Doesn’t Have To)

The Question That Changes Everything (But Doesn’t Have To) “So… are you going to stay technical or go into leadership?” At some point, every developer hears this. And if you’re anything like me, it feels…weird. Because you've spent years getting better at your craft. Writing code. Solving problems. Mentoring a junior or two. And suddenly, people expect you to choose? Like it’s a one-way ticket. But here's the truth: it’s not. The Fork in the Road Isn’t a Trap You’re not choosing forever. You’re choosing where to grow right now. That question, tech or leadership, isn’t about locking yourself in. It’s about finding where you thrive. What gives you energy. What challenges excite you instead of drain you. And you can only figure that out by trying things. What the Technical Path Looks Like Some devs just know: they light up when the problem is hard and the solution is elegant. They want to go deep. Architecture, performance, scalable systems. Becoming the person people turn to when no one else has the answer. They grow into roles like Staff Engineer, Principal Developer, or Tech Architect. Leadership, here, is about technical influence and not managing people. If this path fits you, you might: Lead architecture discussions and code reviews Push for performance and maintainability Mentor others through code, not 1-on-1s Care more about design systems than team rituals What the People Path Looks Like Others, like me, discover joy in helping others grow. In creating clarity in chaos. In connecting devs, product, and design. It’s less about writing the code yourself, and more about creating the environment where great code gets written. Roles here look like Team Lead, Engineering Manager, or Technical Program Lead. If this path fits you, you might: Facilitate retros, standups, and planning Mentor juniors and medior devs Act as bridge between stakeholders and engineers Take ownership of delivery and communication You still code, but often less. And more strategically. Some Myths That Need Busting

May 2, 2025 - 13:43

The Question That Changes Everything (But Doesn’t Have To)

“So… are you going to stay technical or go into leadership?”

At some point, every developer hears this. And if you’re anything like me, it feels…weird.

Because you've spent years getting better at your craft. Writing code. Solving problems. Mentoring a junior or two. And suddenly, people expect you to choose?

Like it’s a one-way ticket.

But here's the truth: it’s not.

The Fork in the Road Isn’t a Trap

You’re not choosing forever. You’re choosing where to grow right now.

That question, tech or leadership, isn’t about locking yourself in. It’s about finding where you thrive. What gives you energy. What challenges excite you instead of drain you.

And you can only figure that out by trying things.

What the Technical Path Looks Like

Some devs just know: they light up when the problem is hard and the solution is elegant.

They want to go deep. Architecture, performance, scalable systems. Becoming the person people turn to when no one else has the answer.

They grow into roles like Staff Engineer, Principal Developer, or Tech Architect.

Leadership, here, is about technical influence and not managing people.

If this path fits you, you might:

Lead architecture discussions and code reviews
Push for performance and maintainability
Mentor others through code, not 1-on-1s
Care more about design systems than team rituals

What the People Path Looks Like

Others, like me, discover joy in helping others grow. In creating clarity in chaos. In connecting devs, product, and design.

It’s less about writing the code yourself, and more about creating the environment where great code gets written.

Roles here look like Team Lead, Engineering Manager, or Technical Program Lead.

If this path fits you, you might:

Facilitate retros, standups, and planning
Mentor juniors and medior devs
Act as bridge between stakeholders and engineers
Take ownership of delivery and communication

You still code, but often less. And more strategically.