From strategy consultant to solo developer. These posts are an honest record of walking away from a stable career, starting over from scratch, and figuring things out along the way.
The posts here follow the path from strategy consulting to unexpectedly taking on a CTO role, and eventually building and running products alone. From why I decided to start over after more than 10 years in one career, to the long hesitation behind walking away from stability, to what it felt like to suddenly carry the responsibilities of a CTO role before feeling ready — these posts are less about polished success stories and more about uncertainty, decisions, and learning things the hard way.
One thing I didn't expect was how much a consultant's habit of overthinking could slow down the process of actually building things. The moments when previous expertise became a barrier instead of an advantage are part of this story too. If you're thinking about changing careers, or struggling with the discomfort of becoming a beginner again, I hope something here feels relatable or useful.
Vibe Pick is still something I'm figuring out one step at a time. It's not a finished story, and maybe that's why I keep writing about it. If any part of these experiences felt familiar to you, even a small word of support genuinely means a lot.
Leaving stability behind wasn’t romantic or brave. It was simply the moment I could no longer ignore what I really wanted.
The Nuance AI Can't Grasp—Localization Secrets That Win the Hearts of Global Users
Breaking an 8-month Stagnation—Why a 'Shitty First Draft' Beats a Perfect Plan
The final decision of an executive on a crumbling ship, and the thirst for "real skills."
How the rigor of a researcher and the agility of a strategist became the foundation of honest code.
In a world where "taking a hint" doesn't exist, how a non-CS strategist designs systems using pure logic.
