Thoughts on vibe coding, AI collaboration, and learning in public.
The Coaching Animator project is maturing — not just in features, but in how I build. SpecKit mastery, design audit discipline, model delegation, and a tentative step toward self-hosted LLMs with LM Studio.
March wasn't a gap; it was the migration from a 'freestyle' hobbyist to a structured systems-builder. A look at the shift from vibe coding speed to structural resilience.
I thought I wanted to share files. Turns out I wanted to share animations. That shift, and a few 'speed-run' lessons, changed everything.
I thought I wanted to share files. Turns out I wanted to share animations. That difference changed everything and then I nearly broke it all trying to move too fast.
Three weeks of shipping fast taught me what I was missing: visibility. Spec-driven development didn't slow me down - it helped me see what the AI was actually building.
Four months in and it's time to reflect on what I've discovered by revisiting some old projects. Refined a rugby app, rebuilt a Pong clone, and rebranded the portfolio site.
Real-time multiplayer isn't just about code. It's about understanding state, timing, and what happens when two players click at once.
The best AI sessions feel like working with a senior dev who occasionally makes stuff up. The trick is knowing when to push back.
Four months ago, coding felt like a locked door. Now I'm shipping real tools. What changed wasn't the technology - it was realising I'd been asking the wrong question.
Copilot taught me I could do this. Claude taught me how to think about it differently.