The 'March Gap' & The Structural Shift
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.
The Hook: Vibe Coding Meets Reality
I thought "vibe coding" was about speed. I was wrong. It’s actually about structure. From February 26th to mid-April, this portfolio went silent. If you look at the commit history, it looks like a hiatus. In reality, it was a reckoning. My workflow wasn't robust enough to survive real life, and I had to stop "freestyling" to build a foundation that actually worked.
The Recognition: When Systems Fail
Let’s be candid: part of the silence was procrastination and broken habits. But the deeper truth? My system was fragile.
The Workflow Leak: Relying on being tethered to a workstation meant that if I wasn't at my desk, I wasn't "building."
The Logic Leak: Trying to parse my life (Obsidian/Goal Tracker) with regex was like building a house on sand. One typo in a markdown file, and the whole system crumbled.
The Technical Pivot: Treating Markdown as Data
In the Goal Tracker App (Next.js 16 / Tailwind 4), I hit the limit of regex-based parsing. I’ve now moved to unified and remark-parse.
By treating my vault as a structured Abstract Syntax Tree (AST), the app transitioned from "reading text" to "understanding hierarchy." It’s no longer a brittle parser; it’s a resilient data engine that treats my ambitions as structured objects.
The Proximity Shift: The AI in My Pocket
The biggest bottleneck was the "tether." By deploying the official Claude Code Discord plugin via the Bun runtime, I’ve moved my pair-programming sessions to the cloud. I can now trigger vault writes and run agentic tasks from my phone while coaching on a rugby pitch. The AI isn't just on my machine anymore; it’s in my pocket.
The Lesson: The Obstacle is the Roadmap
"What stands in the way becomes the way." The friction of mobile access and the fragility of regex weren’t bugs—they were arrows pointing toward the next level of my stack. March wasn't a gap; it was the migration from a "freestyle" hobbyist to a structured systems-builder.