Matt Pocock's Counter-Thesis: The Codebase Is the Agent's Ceiling
Two hours into a full AI Engineer workshop, Matt Pocock arrives at the central claim: "AI is a new paradigm" is the wrong frame for engineering productivity. The real frame is that 30-year-old software fundamentals — small tasks, vertical slicing, TDD, deep modules, observable feedback loops — are more important under AI, not less, because the model's ceiling is bounded by the quality of the code it's working in and the feedback loops you've made available to it. The codebase is the agent's ceiling. Improving the prompt does not raise it.
What the Source Actually Says
The workshop builds a complete production methodology from a Slack-message client brief through publication. The most operationally important pieces:
Smart zone vs dumb zone. LLMs degrade measurably past roughly 100,000 tokens regardless of advertised context window — a 1M context window is "more dumb zone." Pocock monitors token count via a Claude Code status line and designs tasks to fit the smart zone. Compacting is explicitly rejected: it creates sediment that quietly degrades subsequent reasoning. Preferred alternative is clearing context entirely and rehydrating from durable artifacts (PRDs, GitHub issues).
Grill-me before writing anything. A tiny skill that forces the model to interview the developer relentlessly until a shared design concept is reached — typically 40–100 questions. The conversation history is the asset, not the resulting spec. This step is the only one Pocock marks as non-delegatable: "you cannot delegate understanding."
Vertical slices over horizontal layers. AI's natural mode is to code horizontally (all database → all API → all UI), which delays integrated feedback to the third phase. Tracer-bullet vertical slices — thin paths across all layers, visible at the end of each issue — are non-negotiable because feedback-loop quality is the ceiling for AI quality.
TDD as cheating-prevention. Models write implementation first and tests against it if given the chance. Red-green-refactor discipline, with the test authored before the implementation, is structurally harder to game and produces dramatically better output quality on mature codebases.
Strategic Take
The direct challenge to "vibe coding" at scale is timed well — the same week BridgeMind is demonstrating 12-parallel-agent vibe-coding at $128K ARR on a Tauri desktop app. Both produce working software. Pocock's thesis is that vibe coding compounds technical debt at the rate AI adoption compounds feature velocity, and that the debt arrives suddenly when the codebase becomes too shallow for the agent to navigate. The practical entry point is his public methodology repo, which ships the grill-me, PRD, and Kanban skills as ready-to-install tools.