Thoughts on software engineering, web development, and building products.
How I integrated a terminal-native AI coding tool into my daily workflow — hooks, MCP servers, plan mode, and real-world lessons from months of daily use.
How I built a dedicated hosting service that lets Claude publish rich HTML artefacts directly to production — covering subdomain isolation, dual authentication, MCP integration, and the security thinking behind it all.
Next.js uses 308 Permanent Redirect by default. Learn why, how it differs from 301, and where the real SEO problems actually come from — redirect chains, not status codes.
How we built a system that lets AI tools generate and publish structured content directly into production, turning publishing from a manual process into an infrastructure action.
You've spent weeks building your Next.js site. You've deployed to Vercel. Everything looks beautiful. There's just one problem — Google doesn't seem to know your site exists.
I fixed a real production bug in an open-source project, added tests, handled edge cases — and the PR still got closed. Not because the code was wrong, but because product decisions beat engineering.
You deploy your site, it loads fast, Lighthouse looks great — and yet Google refuses to index it. If you're building with Next.js on Vercel, this is far more common than you think.