The Career I Didn't Plan Is the Only One That Makes Sense

I was sitting in my apartment in Islamabad last week, debugging a React component at 11 PM on a Friday, when my friend asked me what I wanted to be doing in five years. I froze. Not because I didn't have an answer, but because I realized my entire career has been a series of accidents that somehow led exactly where I needed to be.

That's when I read Rohini's story about going from theatre to cloud infrastructure to developer advocacy, and it hit different. Not because it's inspirational in that generic LinkedIn way. But because it captures something about how tech careers actually work that we never talk about enough: the best ones aren't planned. They're discovered.

The Accidental Specialist

I started as a frontend developer because I could build things quickly. No grand vision. No ten-year plan. Then one day a client had a real performance problem, and I had to understand how the browser actually works. That rabbit hole led me deeper into performance optimization, then into infrastructure, then into DevOps tooling.

Looking back, I wasn't making strategic career moves. I was following the problems that genuinely interested me. The difference is subtle but crucial.

Rohini's journey mirrors this perfectly. She didn't choose cloud computing because it was trendy in 2009. She saw potential when everyone else saw risk, and that curiosity became her unfair advantage. Her professors noticed her shift because she was actually passionate, not just pivoting fields for better job prospects.

This is something I see missing in a lot of career advice for developers. We're told to plan our specializations, network strategically, build our personal brands intentionally. And yes, those things matter. But they matter after you figure out what you actually love building.

The Community Thing Nobody Plans For

Here's what I find most underrated in her story: the meetups. The weekend talks. The blog posts nobody asked her to write.

In Islamabad, we don't have the same tech infrastructure as Lahore or Karachi. There are maybe three developer meetups per month, and they're inconsistent. For years, I thought that was a limitation. Then I realized it was an opportunity.

I started showing up to whatever meetups existed. I started answering questions on local dev groups. I gave a talk on CSS Grid to maybe twelve people in a cramped office space. Nobody was paying me. Nobody was tracking my "personal brand development."

But something happened. Those twelve people told their friends. People started reaching out asking me to explain technical concepts. I started getting better at teaching because I actually cared about whether people understood, not whether I looked good on stage.

Rohini's Developer Advocate role wasn't a surprise pivot. It was the natural evolution of what she'd been doing for years. She just didn't have the title yet. The title caught up to the work.

What Happens When You Stop Planning

Here's my honest take: the career planning framework fails the moment you factor in actual human growth.

You can't predict what will fascinate you five years from now. You can't know which skills will become valuable or which entire technologies will become obsolete. The only thing you can control is being genuinely curious about the problems in front of you right now.

When Rohini came back from maternity leave, the industry had shifted to AI. Instead of pretending she knew everything, she started "Learning AI Out Loud"—basically admitting what she didn't know and figuring it out publicly. That's braver than any perfectly-crafted career narrative.

I've noticed that the developers I respect most aren't the ones with the perfect GitHub contributions or the carefully curated Twitter presence. They're the ones who ask good questions, admit when they're wrong, and genuinely help other people solve problems. That builds real opportunities faster than any networking strategy ever could.

The Part About Saying No to Expectations

The cultural pressure Rohini faced—the "get married first" expectation—is a different flavor of a universal problem: other people's plans for your career.

In Pakistan, we face this too. The expectation that you follow a prescribed path: school, engineering degree, corporate job, stability. Deviation gets read as irresponsibility.

But here's what I've learned: your career is too personal to let someone else's risk tolerance determine it. Rohini boarded that flight to Cape Town with two suitcases and one contact. That wasn't recklessness. That was trusting her own judgment more than the cultural script.

Your Move

So what now? If you're reading this and thinking your current path feels imposed rather than chosen, that's a signal worth listening to.

Start exploring what actually interests you. Write about it. Talk to people about it. Build something small. The career usually reveals itself through these small acts of genuine curiosity, not through five-year plans.

What's the work you've been doing on nights and weekends that nobody asked you to do?

Source: This post was inspired by "Theatre Kid to Developer Advocate, None of This Was Planned" by Dev.to. Read the original article