BLOG

I asked an agent to audit my repo. It found my .gitignore ignoring package-lock.json, Dependabot alerts off, and ~40 stale branches.

In April I wrote that the ProjectGrid component was the unlock. I built it, measured it against the demo problem, and landed on a different next step: a real demo site.

Every tag on my blog had to pass one test: does it anchor a real series? 30 tags died. 11 survived. Here's the rule, the audit, and the Velite validator keeping tags honest.

Three parallel subagents, ten open Projex issues, one release. I skimmed the diffs at the end, not in the middle.

Ubuntu 24.04's ESM pin (priority 510) outranks GitHub's apt repo (500), so Ubuntu's broken 2.45.0 kept winning the candidate slot. Three layers of failure: a GraphQL deprecation message that was actually the error, GitHub's repo URL, and the ESM pin itself.

Container isolation wasn't actually working. Sage was running two Hermes instances, cron jobs vanished into the wrong database, Telegram refused to send. I fixed all of that. Then the real bug turned out to be a Python loop that was never Docker's fault.

I ran three Hermes gateways as separate profiles on the same machine. Replies came from the wrong profile, Telegram connections fought each other. Here's why I containerised each one — and why that was only half the story.

Hermes couldn't load half the links I sent it. Found Camoufox through a Reddit thread, then hit a Firefox sandbox issue that killed tab creation before I got anywhere.

After a deep code review with my AI agent, I realised the code wasn't the problem. The problem was I couldn't figure out how to show anyone what I'd built.

Projex is my internal tool for managing my projects page. Its config file is TypeScript. Hand-editing it was only a matter of time before I broke something. So I built a CLI instead.

I built Projex to showcase projects on my site. The first time I tried using the dev.to integration, nothing worked. Tests passed. Types checked. Stats were completely broken.

An essay making the rounds argues that 'follow your passion' is bad advice. But it conflates accepting your circumstances with choosing them, and that distinction matters.

Straico's API gives me access to 90+ AI models through one key, but it doesn't support streaming or function calling. OpenCode needs both. I built a proxy to bridge the gap and it turned into way more than I planned.

I ran npm update, verified the new version was installed, but package.json still showed the old version. That sent me down a rabbit hole trying to understand how npm actually manages versions.

I set up granular bash permissions for my OpenCode subagents, but every command still prompted for approval. Turned out to be three separate issues stacked on top of each other.

209 commits. A rename mid-flight. Publishing pipelines that broke for two days straight. And zero blog posts while any of it happened.

Some hobbies give you community. Some hobbies break the promise of community entirely. I've been thinking about why.

Obsidian Sync costs $120 a year. I wasn't paying for yet another subscription. So I set up Syncthing with my always-on NucBox as the hub. Here's what I learned about the bits most guides skip.

Most build-in-public advice stops at 'just keep showing up.' But what you're building with that consistency matters as much as the consistency itself.

I built a skill that enriches book passages with historical context, pop culture connections, and thematic insight. Here's how it works and why I keep using it.

On reactive days, invisible work, and protecting time for thinking.

The specific kind of demoralizing that comes from building something, sharing it for free, and getting nothing back.

Anthropic contributed MCP to the world while locking down Claude subscription access and sending legal letters to open source projects. I use one of the tools they targeted.

I've had blogs before. Let them die. This one's about documenting what I build and what breaks along the way.

First time really trying to use opencode inside tmux on WSL2. Hit Esc to interrupt an agent and nothing happened. Couldn't scroll properly. Couldn't copy to clipboard. Here's what finally worked.

The irony of debugging Velite watch mode: I restored code that was intentionally removed to fix double builds. Here's what happened.

I wanted to start fresh on X, but my history was flooded with content I no longer cared about that I had retweeted years ago. Sketchy deletion tools wanted my credentials. So I built a ZeroWork TaskBot to delete everything instead.

Velite's draft filtering wasn't working in production. Here's what I tried, why it failed, and what finally fixed it.

I tried to make a slash command call another slash command in OpenCode. It doesn't work. Here's what I discovered and how I consolidated two duplicate commands into one.

Got 'fatal: loose object is corrupt' when running git log. Three empty object files, repository broken. Here's how I recovered everything using git fetch and why moving files instead of deleting them was right call.

I wanted to hide draft posts in production. Thought I could just add draft: true to frontmatter. Turns out Velite needs explicit schema definition AND filtering logic.

I broke my entire blog review system trying to reduce prompt overhead so I could fit more messages into Claude's session limits. My 'optimization' saved 1,100 tokens but cost me 5 hours of debugging. Here's what I learned about premature optimization in multi-agent systems.

I thought auto-accept edits mode was broken. Turns out it's a security feature protecting Claude Code's configuration files - and here's why that's actually brilliant.

I wasn't updating my CLAUDE.md file enough. When I asked Claude to do it, I got bloat. So I built a multi-agent debate system where AI argues with itself to keep instructions lean.

How I created a four-agent workflow system to transform raw notes into authentic blog posts - complete with debates, convergence protocols, and real expert frameworks.

Added @tailwindcss/typography to fix bullet points. It worked, but suddenly headings and code blocks looked terrible. Here's why plugins aren't always the answer.

I bought an Asus RT-BE88U router to replace my ISP's Fritzbox WiFi. What I thought would be simple turned into a two-hour networking adventure. Here's what tripped me up.

After upgrading Unraid from 6.9 to 7.0.1, all my Docker containers became unmanageable - marked as '3rd party' and locked out of updates. Here's how I fixed it without recreating everything.

I added a career timeline to my About page. Not for a resume, but because building it taught me something unexpected about both code and career. Here's what I learned.

I wanted to add syntax highlighting to my Velite/Next.js blog using Shiki. Seemed straightforward - install packages, configure, done. Wrong. Here's what went wrong and how I fixed it.

Spent hours debugging Velite with Next.js 16 - wrong imports, watch mode not working with Turbopack, async params, and more.

I keep having business ideas and not executing on them. Then someone else ships the same thing. The Noah Kagan quote that made me cringe.