Choosing Curiosity Over Career Optimization

The Wake-Up Call

I’ve spent years optimizing for my career. Learning the right frameworks. Building the right projects. Networking with the right people. And somewhere along the way, I stopped asking myself what I actually wanted to explore.

I’m not a beginner anymore. I’m not chasing my first job or trying to break into big tech. I’m at a point where I can build most things I set my mind to. But here’s what I’ve realized: I’ve been so focused on being a better developer that I forgot to be a more interesting person.

The Cost of Being Quiet

For most of my career, I’ve been the quiet one. Head down, code focused, avoiding the spotlight. I told myself it was about letting my work speak for itself. But the truth? I missed opportunities because I wasn’t willing to speak up, share what I knew, or put myself out there.

I watched others with less experience get recognized because they were willing to talk about their work. I saw people build networks and opportunities simply by being visible. And I stayed silent, thinking that was somehow more noble.

It wasn’t noble. It was fear dressed up as humility.

The Shift

AI didn’t make me question my career—it made me question my priorities.

When I see AI generate entire applications in minutes, my first thought isn’t “I’m replaceable.” It’s “Why have I been spending all my energy on things that can be automated?” The real question isn’t about job security. It’s about what I want to do with my time on this planet.

And the answer isn’t “optimize my career trajectory.” It’s “explore things that make me curious.”

So I started doing things differently. I started hiking—getting out of my apartment and into nature. I started attending social gatherings instead of declining every invitation. I bought a small displacement bike to stop relying on others for transport and, more importantly, to stop dealing with matatus and the constant battle against dust. It started as a practical fix for a daily frustration, but it turned into something that makes me feel alive.

These aren’t just hobbies. They’re proof that I’m choosing to live, not just exist between sprints.

What I Actually Want

I want to learn things just because they’re interesting, not because they’ll look good on a resume.

I want to write about what I’m discovering, not to build an audience, but because articulating ideas helps me understand them better.

I want to teach, not because I’m an expert, but because explaining things to others forces me to truly grasp them myself.

I want to be outspoken about what I’m learning and experiencing—not in a performative way, but because staying silent has cost me too much already.

I want to leave something behind—however small—that shows I was here, I was curious, and I tried to make sense of things.

This isn’t about becoming an influencer or building a personal brand. It’s about reconnecting with the part of me that got into tech because it was fascinating, not because it was lucrative.

Why Content Creation?

Content creation isn’t a career pivot for me. It’s a practice of self-discovery and a way to finally use my voice.

When I write, I’m forced to clarify my thinking. When I teach, I’m forced to understand deeply. When I explore new technologies and document the journey, I’m giving myself permission to be curious without the pressure of immediate utility.

And when I share publicly, I’m practicing being outspoken—something I should have started years ago.

I’m not trying to compete with the polished tutorials from big tech influencers. I’m just trying to think out loud, share what I’m learning, and maybe help someone else who’s a few steps behind me on the same path.

The Real Reason

Here’s the honest truth: I’ve been neglecting myself.

I’ve been so focused on being productive, on shipping features, on leveling up my skills, that I’ve forgotten to ask why. Why am I doing this? What do I actually care about? What would I explore if I wasn’t worried about whether it would advance my career?

Content creation is my way of answering those questions. It’s a forcing function for curiosity. It’s permission to explore without justification. It’s a way to leave a mark that’s mine—not just code that will be refactored or features that will be deprecated.

And it’s my way of finally being visible, of using my voice, of sharing what I know instead of keeping it locked away.

Moving Forward

I’m not quitting my job. I’m not abandoning software development. I’m just refusing to let my career consume my entire identity.

I’m going to write about what I’m learning. I’m going to explore technologies that intrigue me. I’m going to share my process, my failures, my half-baked ideas. Not because I think I have all the answers, but because I’m tired of pretending I do.

I’m going to keep hiking, keep riding, keep showing up to gatherings. I’m going to keep choosing experiences over optimization.

If you’re reading this and feeling the same exhaustion—the sense that you’ve been optimizing for the wrong things—I see you. You don’t need permission to explore. You don’t need to be an expert to share. You just need to be honest about what you’re curious about.

And if you’ve been quiet like me, know this: your voice matters. The opportunities you missed because you stayed silent? They’re still out there. Start speaking.

Let’s stop optimizing and start exploring.

---

This is the beginning of a new chapter. If you’re on a similar journey, I’d love to hear about it.