This is a submission for the 2026 WeCoded Challenge: Echoes of Experience
Here's a story from my own journey.
There's a version of this story where everything falling apart is the lowest point.
It's not.
A New City, A New Job, A Slow Unraveling
My second job came with a lot of firsts — a new city, a new culture, a completely unfamiliar environment. New food, new language, new people.
At first, it was exciting.
But slowly the pressure started building. I was trying to adapt to a new workplace, understand unfamiliar systems, and fit into a culture I was still figuring out.
Somewhere along the way, I lost my footing.
I could feel it. I wasn't performing at my best, and the gap between what I expected from myself and what I was delivering kept growing.
Eventually, I realized the role probably wasn’t the right fit for me — I was spending more energy just trying to keep up than actually learning.
I was one day away from leaving.
Then the job didn't work out, and suddenly that decision was made for me.
That job had been the only thing connecting me to that city — losing it meant suddenly feeling disconnected from everything around me.
When Direction Disappears
What followed was a strange period.
Logically, I knew the situation wasn't right for me anyway.
But emotionally it still hurt.
It was the first time in my career that something had clearly failed.
For a while I kept doing what you're supposed to do — applying for jobs, preparing for interviews, trying to learn new things.
But underneath all that activity there was a deeper problem.
I had lost my sense of direction.
The hardest part of that phase wasn't rejection or uncertainty.
It was waking up and not knowing what the next meaningful step should be.
The Mantra I Had Forgotten
During that time, I remembered something I used to tell myself earlier in my career:
I don't wake up every day just to go to a job.
I wake up to be better than my yesterday self.
Somewhere in the pressure of trying to "keep up," I had forgotten that.
The difficult period forced me to rediscover it.
Building Stupid Things Saved Me
When I eventually went back to my hometown to reset, I stopped trying to follow a perfect plan.
Instead, I started building things again.
One of the first things I made was a GTA-inspired clone — not because anyone asked for it, not because it would help me get hired, but simply because I wanted to see if I could build it.
It had no ROI. No roadmap. No expectations.
But something unexpected happened.
It reminded me why I started building software in the first place.
Not for job titles.
Not for resumes.
But because creating something from nothing is deeply satisfying.
That small project gave me back something I had quietly lost: confidence.
The Turning Point
As I started applying again, I began noticing a shift.
Frontend roles were becoming harder to find, and the ones that existed were increasingly looking for senior profiles or broader skill sets.
The industry was changing faster than I had expected.
I realized I had two options:
keep trying to force the same path forward — or start adapting.
That's when I stopped asking:
"Will AI replace developers?"
and started asking a different question:
"How can I learn to work with it?"
That one shift in thinking changed everything.
The Mess Nobody Talks About
Learning AI turned out to be far messier than I expected.
I jumped between courses. Restarted multiple times. Tried different approaches and often felt like I was moving in circles.
Eventually I realized the confusion wasn't a sign I was failing — it was simply what learning something new looked like, especially in a space evolving this quickly.
And if I was struggling to find a clear path, chances were others were too — and maybe we could figure it out together.
That’s what learning in public is really about.
That's what led me to start writing on Dev.to and building my presence on X — not because I had answers, but because sharing the messy process felt more honest than pretending the path was clear.
Over time, that also taught me something important:
Building skills matters.
But being visible while you build them matters just as much.
A Different Way To Look At That Year
Looking back now, I see that period very differently.
At the time, it felt like unemployment.
But now I think of it more as a pause — a limited one — that gave me space to experiment, learn new technologies, and rethink the direction I actually wanted to take.
During this period, I started exploring AI, building projects, and eventually launched my first Chrome extension on the Web Store. The moment it went live, I genuinely thought: did that actually work?
It wasn't a startup. It wasn't viral.
But it was real. It was mine. And it existed in the world.
That mattered.
The Real Lesson
If there's one thing that year taught me, it's this:
A job can define your role — but it can't define you.
I had to build that identity myself: publicly, imperfectly, one post and one project at a time.
The unexpected turn my career took didn't end my journey — it clarified it.
Careers in tech rarely follow a straight line.
Sometimes the path disappears.
And when it does, you're forced to stop following one — and start building your own.
Stop waiting for the perfect roadmap. Start building one.
Top comments (1)
This is great. I wish you luck in your journey. Thanks for the nice experience you've shared in this article