DEV Community

Cover image for What I Wish Someone Told Me Before I Learned to Code at 25
Jake Mittal
Jake Mittal

Posted on

What I Wish Someone Told Me Before I Learned to Code at 25

I didn't grow up dreaming of being a developer. At 25, I had two degrees, zero job offers, and a growing suspicion that the plan I'd spent years building wasn't going to work.

I'm writing this for anyone in the DEV community who came to programming late, sideways, or out of necessity rather than childhood passion — because I think there are more of us than the "I wrote my first line of code at age 8" stories would suggest.

The trap I didn't see coming

Before I get to the code part, I have to talk about the thing that almost stopped me from getting there.

I'd worked hard for two degrees. As an immigrant in the US, that effort felt even heavier — it wasn't just time, it was a bet on a whole life plan. So when those degrees didn't open the doors I expected, my instinct wasn't to change direction. It was to push harder in the same direction. Apply to more jobs. Wait longer. Justify the investment.

That's the sunk cost fallacy, and it's sneaky because it disguises itself as loyalty and grit.

The sentence that changed my direction

A friend said something to me that cut through all of it:

"In life, we must choose our regrets: 6 years pursuing the wrong degrees, or 40 years in the wrong career. You decide."

That's when I stopped treating my degrees as a debt I had to repay with my career and started treating them as sunk cost — already spent, not refundable by staying miserable.

What actually learning to code looked like

No bootcamp scholarship, no CS background, no safety net. Just me, some free resources, and a lot of confusion in the beginning that I assumed meant I wasn't cut out for it (I was wrong — that confusion is just what learning looks like).

A few things that helped, if you're earlier in this than I was:

I stopped comparing my week 1 to someone else's year 3
I built small, embarrassing projects instead of waiting to feel "ready"
I treated every error message as information, not judgment
I accepted that starting later meant catching up on syntax, not on capability

If you're reading this wondering if it's too late

It's not. Compare your regrets the way my friend made me compare mine. A few years of feeling behind is temporary. Decades in the wrong path is not.

The best time to start was yesterday. The next best time is now.

Top comments (0)