Simon Willison Admits the Line Between Vibe Coding and Real Engineering Has Collapsed

Simon Willison published a blog post today that crystallized something I've been feeling for months. The clean distinction between vibe coding (non-programmers using AI without review) and agentic engineering (professionals maintaining standards) doesn't hold up anymore. Not even for him.

Willison now treats Claude Code output like code from another team in a large organization. A semi-black box he trusts until it breaks. He's not reviewing every line. He evaluates by proof-of-use (did it actually work?) rather than code-quality metrics like test coverage or documentation.

This is a big mental shift from someone who's arguably the most respected practitioner voice in the AI tooling space. And I think he's right. When your output jumps from 200 to 2,000 lines per day, you physically can't review everything at the same depth. The math doesn't work.

Here's what troubles me about it, though. We built entire engineering cultures around code review as a quality gate. PR reviews, pair programming, style guides. All of it assumes humans read and verify code before it ships. Willison's trust model acknowledges that gate is already broken for most practitioners using AI tools. We just haven't updated the processes around it.

His key insight: productivity jumping 10x demands upstream redesign of processes built around expensive engineering timelines. If generating code is nearly free, the expensive parts become architecture, verification, and taste. Sound familiar? That's exactly what ProgramBench proved quantitatively.

For builders, here's what I'd suggest. First, treat agent output like you'd treat a contractor's code. Run the tests, verify the behavior, but don't pretend you're auditing every token. Second, invest more time in specifications and architecture documents. If the agent is writing 90% of the code, the spec is where you add value. Third, build better automated verification. Tests, type checking, linting, integration tests. These are your actual quality gates now, not human code review.

The trust gradient Willison describes isn't a lowering of standards. It's an honest acknowledgment of where standards actually live in an AI-augmented workflow.