↓Skip to main content
Zeitgeist — a spike by Chris Gathercole
  1. Topics/
  2. Vibe Coding Approaches/

Gather — 18 May 2026

Willison — Productive Tension at the Boundary #

  • Vibe coding and agentic engineering are getting closer than I’d like (Simon Willison, 2026-05-06) — Willison’s post-conference reflection: the boundary between vibe coding and agentic engineering is blurring in practice. Claude Code for web and Codex Cloud share the same user flow as vibe coding (describe a goal, come back to results) but have the complexity of production agentic systems underneath. His concern: professional engineering discipline gets confused with casual vibe coding as the UIs become identical. The risk is not that vibe coding looks like agentic engineering — it’s that agentic engineering starts to feel like vibe coding to practitioners.
  • Agentic Engineering Patterns (Simon Willison, 2026-02-23) — Willison’s living guide to engineering practices for coding agents, modelled on the Gang of Four Design Patterns book. Key chapters: automated testing as a prerequisite (not optional), advance planning with documented specifications, disciplined version control, and “closing the feedback loop tightly” (surface only failures, silence successes). Explicitly not a prompt engineering guide — a professional practices document for engineers working with agents.

Production Scale — Named Organisation Metrics #

  • Why Agentic Engineering Must Replace Vibe Coding (DEV Community) — First named-organisation production metrics for agentic coding at scale: TELUS saved 500,000+ hours with 13,000 AI-built solutions; Zapier at 89% AI adoption across the entire organisation; Stripe’s “Minions” agents produce 1,000+ merged PRs per week. These are operational numbers, not pilot projections. First time named organisations have published production (not pilot) agentic coding metrics at this scale.
  • Claude-Specific Expertise Willison’s “getting closer than I’d like” concern is directly about Claude Code for web — the async cloud agent’s UI is indistinguishable from vibe coding even when the underlying task is a professional engineering workflow.
  • Applications of Vibe Coding TELUS/Zapier/Stripe are the concrete enterprise evidence the adoption story has been missing — operational numbers from named organisations, not projections.

Meta-observations #

  • Emerging pattern: The vibe-coding/agentic-engineering boundary is now a practitioner risk, not just a vocabulary distinction. Identical UIs producing structurally different outcomes. Willison’s piece is the first to frame this as a risk rather than a definitional debate.
  • Quality signal: Willison’s Agentic Engineering Patterns guide is in the same authority tier as Osmani’s comprehension debt piece — a practitioner with credibility documenting patterns practitioners are independently discovering. Treat as a reference document.
  • Keyword suggestion: "agentic engineering patterns" site:simonwillison.net — the guide is updated continuously; future chapters will generate cross-topic coverage.