The PM who became the developer

My tech timeline runs backwards.

Most people go junior dev → senior dev → lead → manager → "why am I in meetings all day." I did the whole thing in reverse: internet pioneer → founder (a few times) → product director → team lead → burnt-out exec → "wait, let me try coding" → solo dev.

Yes, backwards. No, I don't regret it.

The long runway

I was on the Windows 95 launch team before it shipped. I ran nopay.net, handing out free internet access on 1.44MB floppy disks — which, if you're under thirty, is a story that requires three separate footnotes. I hand-coded HTML back when <marquee> was considered a design flex. I had one of the first ~50,000 Hotmail accounts and, God help me, an ICQ number.

For twenty-five years I was fairly technical. I could read code, argue about architecture, and smell a doomed estimate from across a room. What I had never actually done was write the software myself. I was always the person describing the feature, never the person building it.

I told myself that was fine. I was the "what and why" guy. Let the engineers handle the "how."

The plot twist

Then lockdown happened.

Stuck at home in 2020, staring down the choice between learning something or watching another season of television, I finally sat down and learned full-stack development. Properly. Not "I did a tutorial once" — actually shipping things that ran.

Turns out spending decades as the non-developer in the room makes you a strange kind of developer:

• I build features like someone who has sat through a thousand feature-request meetings — because I have. I know which "small tweaks" are landmines.
• I debug like someone who has been on the receiving end of vague bug reports — also me. So I write the reproduction steps I always wished I'd been handed.
• I write documentation like someone who genuinely wants it to be read, which, revolutionary as it sounds, changes everything about how you write it.

The judgment I'd built as an operator didn't go to waste. It compounded. Knowing what to build was suddenly ten times more valuable now that I could also build it — no translation layer, no telephone game between the idea and the code.

What I actually do now

I'm in Bangkok, shipping SaaS solo. My stack leans modern and AI-native — TypeScript, Next.js, Convex, Turborepo, and a workflow that treats AI tooling as a genuine force multiplier rather than a novelty. I run MVPLaunch (your MVP, shipped in four weeks), I'm building something in stealth called Dojo, and there's always a "whatever's next."

If there's a lesson buried in the backwards timeline, it's this: the boring decades weren't wasted. Every terrible pivot meeting, every doomed roadmap, every "why is this taking so long" — that was all tuition. I just paid it before I knew what I was buying.

The PM became the developer. Best plot twist yet.