Claude Fable 5 Review: A Beast That Eats Your Limits
Fable 5 refactored my app like a senior dev, then ate my 5-hour limit. The quality jump is real, the token burn is brutal, and there's a trust problem. →
Web Development
I share my experience and knowledge about web development, best practices, and the latest technologies.
Fable 5 refactored my app like a senior dev, then ate my 5-hour limit. The quality jump is real, the token burn is brutal, and there's a trust problem. →
Grilling, PRDs, vertical slices, conditional TDD and a slim AGENTS.md. The five-skill pipeline I run on every feature, built on Matt Pocock's agent skills. →
Boris Cherny's job now is writing loops, not prompts: agents that prompt agents. What that means, how to build one in Claude Code today, and where it breaks. →
A CLI + MCP server that configures GA4 and Search Console from YAML, and flags what to check in your SEO by impact. Deterministic: you make the calls. →
Explore more content about web development and technology.

Three weeks pairing Gemini Flash with Claude Code on side projects: 90% of my tests are now AI-written and I ship 3-4x faster. What worked, what broke. →

I upgraded this site from Astro 5 to Astro 6. The breaking changes that bit me: content.config.ts, the slug to id trap, Zod 4 defaults, removed APIs. →

A week with Gemini 3 Pro: Deep Think on a real migration, a bug diagnosed from a 2-minute video, and the agentic stuff that still needs a babysitter. →

Google Antigravity vs Cursor: honest verdict after a week with the agent-first IDE. Parallel agents, memory leaks, and which VS Code extensions survive. →

One good example beats a paragraph of instructions: how one-shot prompting and context placement (start or end, never the middle) fix vague AI answers. →

Astro schema fields missing at runtime? You're probably editing src/content/config.ts instead of src/content.config.ts. Symptoms, cause, 4-step fix. →

Astro 6 is here. Hands-on with Islands and the Content Layer API, plus the real Next.js to Astro migration that pulled most of the JS off my portfolio. →

Tailwind CSS 4 rebuilt the engine in Rust: ~5x faster full builds, 100x+ faster rebuilds. What broke migrating 3 production projects, the setup that works. →

A strict tsconfig.json and advanced types took our production bugs from 47 to 3 in six months. The setup, the types that did the work, and where it hurt. →

Tests pass locally but fail on Vercel? The real fix is one line: NODE_ENV in vitest.config.ts, plus CI-aware timeouts. My 4 wasted hours, condensed. →
Follow me on social media to not miss any article and stay updated on the latest news in web development.