Why I Don't Want to Be "Just" a Software Developer Forever

This is something I've been thinking about a lot lately.

When I started learning to code, my goal was simple: get a good developer job, keep improving, and earn a better salary. Like many of us, I thought that was the finish line.

But after working in tech, I realized something about myself.

I enjoy building things, but not just software.

I get excited by products, brands, solving real problems, and the idea of creating something that people genuinely use. Coding feels like a superpower to me, not the final destination.

Don't get me wrong, I love writing code, learning new technologies, and improving as a developer. Those skills have completely changed my life. But if I picture myself 10 years from now, I don't see myself saying, "I just want to keep climbing the developer ladder."

I see myself building something of my own.

Maybe that's a product.
Maybe it's a business.
Maybe it's something I haven't even thought of yet.
(not necessarily in tech)

Right now, I'm still working, still learning, and still trying to become a better developer. I don't have all the answers. I'm simply becoming more honest with myself about what I want in the long run.

So I'm curious...

Has anyone else felt this way?

Did you start your career as a developer but eventually realize you wanted to build a business or a product instead?

If you've been through that transition—or you're thinking about it too—I would genuinely love to hear your story and any advice you have.

I'm here to learn.

Comments

[Local Plugins]

Yes, and I'm somewhere in the middle of it right now, so this is less advice than a field report.

I had the same realization: code is the tool, not the destination. What I actually like is making a thing exist and having someone use it. So I started shipping small products of my own.

Here's the part nobody warned me about. Building is the easy half. I can build a thing in a week. Getting even one stranger to use it has taken far longer, and it's a completely different skill that has nothing to do with being good at code. Distribution, positioning, writing something people actually want to read, being patient while nothing happens. Being strong at engineering buys you almost none of it, and the feedback loop is brutal compared to a compiler telling you you're wrong in two seconds.

So the honest version: the "build a product" life is mostly not building. If what you love is the making, that's worth knowing before you reorganize your career around it. I still think it's worth it. Just go in clear-eyed about the ratio.

The good news is the developer skill isn't wasted. It just stops being the point, and becomes the cheap part.

Good luck. It's a real question, and asking it honestly beats defaulting up the ladder.

[Preeti yadav]

Thanks for sharing this, it really resonated with me. I'm curious: if you could go back, what's one thing you'd start learning earlier besides coding? Marketing, sales, talking to users, or something else?

[Klaudia Grzondziel]

I've had similar reflections recently. Learning to code was always the goal that was supposed to open doors for more opportunities. But somewhere along the way, I discovered that it was just a "productive procrastination" from what I always wanted but was always afraid to follow – arts. I literally dream of days when I can freestyle paint or go back to writing a book. Arts will not pay my bills, though 😅

[Preeti yadav]

I really like the phrase "productive procrastination." It perfectly captures how something valuable can still not be the final destination.

I hope you find a way to make room for both, coding for stability and art for fulfillment. Who knows? Maybe one day your art will pay the bills too. 😊