The author of Clean Code spent decades reminding us that reading code is most of the job. This week he said he stopped reading what his agents write, and that confidence comes from somewhere else: a gauntlet of constraints made of tests, metrics, mutation testing and coverage. I agree, and I explain with the caveats that matter: the gauntlet has an anatomy, and the human's role shifts from inspector to designer.

The agent writes in twenty minutes, you spend the afternoon reviewing: generating code got cheap, verifying stayed expensive, and you became the bottleneck. After more than a year refining a guideline for developing with agents, this is the philosophy and practice of what I call Spec-Anchored Agentic Development: one spec per capability as the anchor of verification, context in three layers, the machine giving the first no before any human review, and autonomy earned per class, with evidence instead of faith.

What takes down your biggest sale of the year isn't total load, it's the hot key: one hot partition that throttles while the rest of the table sits idle. Space-based architecture fixes that by taking the database out of the critical path. On AWS serverless you inherit the principle, not the literal implementation, and most projects don't even need it.

The biggest mistake in serverless architecture isn't technical, it's organizational. Without Domain-Driven Design, you sell team autonomy and deliver the opposite: a distributed monolith dressed up as microservices.

The difference between the architect who applies patterns and the one who understands them is the same as between the coach who copies formations and the one who understands the game.

Discover how AWS Lambda Durable Functions lets you create workflows that pause, wait for human approvals, and resume after hours - without paying for wait time.