We're talking about cognitive debt. We should also be talking about operational debt: code generated faster than teams can earn the knowledge to run it.

My full process for AI-augmented development, built from daily use in production. Field reporting from a practitioner, not theory.

AI has scaled code production dramatically. Human review capacity hasn't changed. Here's how to allocate the scarce resource.

AI coding tools let you build in a weekend what used to take months. But you can't learn to operate what you've built at the same pace. The gap is where trust breaks.

I used an AI to build bot protection, and it says something about how the scale of a weekend project has changed.

Jeff Huber makes the case that the central discipline of building AI systems isn't prompting, isn't RAG, it's context engineering. Here's what that means and why I think he's right.

AI-assisted coding has changed how I approach problems. The real leverage is in research and planning, not implementation.