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

Vibe Coding Approaches

What We’re Tracking #

The evolving landscape of AI-assisted “vibe coding” — techniques, tools, frameworks, and methodology. Includes IDE-based tools (Cursor, Windsurf, Copilot), agent frameworks (LangGraph, CrewAI, AutoGen), and emerging practices like spec coding, multi-agent orchestration, and prompt-driven development. Focus on genuine technique over tool roundups and marketing content.

Config: journals/topics/config/vibe-coding.yaml

Index #

2026-06-26 — Gather #

Agentic Engineering: Methodology Crystallising #

  • Agentic Engineering: The Complete Guide to AI-First Software Development (NxCode, 2026) — Positions agentic engineering as the professional successor to vibe coding, centred on four practices: spec-first design, the Ralph loop prompt cycle (Requirements → Assess → Loops → Plan → Habits), layered testing, and cross-model validation. The Ralph loop is the first named prompt-cycle methodology for agentic engineering distinct from the broader “spec-driven” framing — practitioner-level detail missing from Karpathy’s original framing.
  • Sequoia Ascent 2026 summary (Andrej Karpathy, 2026) — Karpathy’s first-person summary of his Sequoia AI Ascent talk: describes the December 2025 inflection point where models started producing chunks he couldn’t improve, frames “agentic engineering” as the discipline that preserves quality while agents raise the capability ceiling. Primary source supersedes the secondary coverage already captured in prior entries — the first-person account includes framing not present in other coverage.

Tool Landscape: Post-Fable 5 Reassessment #

  • Best AI Coding Tools June 2026: Updated After Fable 5 Changes Everything (Developers Digest, 2026) — Reassessment of the coding tool landscape after Claude Fable 5’s June 9 launch: “completed equivalent work with fewer tool calls and lower token consumption” in autonomous workflows. Windsurf rebranded to Devin Desktop on June 2 (Cognition’s repositioning around an Agent Command Center surface). Updated comparative positioning: Claude Code as collaborator, Cursor as explorer, Devin Desktop as value tier.
  • Cursor vs Windsurf vs Claude Code in 2026: The Honest Comparison (DEV Community, 2026) — Practitioner three-way comparison after sustained use: “Windsurf rebrand to Devin Desktop on June 2” confirmed; Cognition repositioning around Agent Command Center UX. Claude Code characterised as better at context-aware collaboration over long sessions; Cursor better at rapid exploratory edits; Devin Desktop better value for self-contained tasks with clear endpoints.
  • Top Agentic Frameworks for Building Applications 2026 (JetBrains, 2026-06) — LangGraph as the emerging production standard for agentic application frameworks, with LangChain and AutoGen prominent alongside newer open-source entrants. JetBrains’ developer tooling perspective gives a framework-selection lens distinct from the coding-tool comparisons above.

Comprehension Debt: Failure Mode Framing Matures #

  • Vibe coding can build your pipeline. It can’t explain it six months later. (VentureBeat, 2026) — Vibe coding’s core failure mode is not delivery speed but comprehension: pipelines built by AI prompt-chaining pass tests and ship features, but nobody owns them six months later. Draws a direct line from vibe coding to comprehension debt as an organisational risk, not just a codebase quality problem — when the pipeline author leaves, the knowledge gap is a business risk, not just a tech debt entry.

Legitimisation Signals #

  • VibeX 2026 — 1st International Workshop on Vibe Coding and Vibe Researching (EASE 2026) — First academic workshop dedicated to vibe coding methodology, co-located with EASE 2026. Academic recognition signals the field has reached sufficient maturity and controversy to warrant formal inquiry — a legitimisation milestone analogous to when “technical debt” gained academic treatment.
  • Google and Kaggle’s GenAI Intensive Vibe Coding course (Google, June 2026) — Structured vibe coding course launched in June 2026 by Google and Kaggle, formalising prompt-first development techniques for non-engineers. The institutional scale (Google’s platform + Kaggle’s developer community) represents the largest organised effort to teach AI-first coding methodology to non-traditional practitioners.
  • [vibe-coding-applications] VentureBeat’s “pipeline ownership” framing maps directly to the organisational comprehension debt cases; the six-month horizon is when governance gaps materialise as business risk.
  • [claude-expertise] Karpathy’s December 2025 inflection description (“chunks I couldn’t improve”) is the practitioner analogue to Willison’s Fable 5 observations (proactive, silent refusals) — both describe the same capability threshold from opposite valence perspectives.
  • [open-vs-closed-ecosystems] Windsurf → Devin Desktop rebrand (Cognition) and the JetBrains framework survey both indicate the tooling layer is consolidating around Claude Code, LangGraph, and agent-native architectures, regardless of which model is underneath.

Meta-observations #

  • Emerging pattern: The Ralph loop (NxCode) is the first named prompt-cycle methodology for agentic engineering. Naming methodologies is how a practice discipline crystallises — expect “Ralph loop” to appear in other guides if the term takes hold.
  • Keyword suggestion: “Devin Desktop” — Windsurf’s rebrand to Devin Desktop (June 2) is not yet reflected in this journal’s existing keywords. The Devin Desktop positioning (Agent Command Center surface) represents a distinct UX paradigm from IDE-embedded tools.

2026-06-19 — Gather #

Adoption Data & Productivity Paradox #

  • AI Coding Adoption 2026: 50 Statistics From 7 Surveys (Digital Applied, 2026) — Claude Code at 24% adoption in US/Canada, co-leading with Cursor at 18% globally. 84% of developers report using or planning to use AI coding tools; 51% use them daily. Controlled experiments show 30–55% improvement for scoped tasks (writing functions, tests, boilerplate), but organisational productivity improves only when process bottlenecks are also addressed.
  • AI Coding Impact 2026 Benchmark Report (Opsera, 2026) — The productivity paradox in data: AI generates 42% of code; PR cycle times are 20% faster; but incidents are up 23.5% and failure rates up 30%. Developers feel 20% more productive but are measurably 19% slower when review overhead and bug rates are factored in. This is the clearest quantification yet of the comprehension-debt dynamic tracked since May 2026.
  • Vibe Coding Trends 2026: Adoption, Productivity, and Code Quality Data (Keyhole Software, 2026) — 92% daily AI tool adoption with only 29% trust; 41% increase in bug rates post-adoption. The trust/adoption gap is the widest observed metric discrepancy in this topic. Developers are using tools they don’t trust, which itself signals institutional pressure rather than individual confidence driving adoption.

Tooling #

  • Vibe Coding Is Dangerous, Agentic Engineering Isn’t ft. Wes McKinney (MotherDuck, 2026) — Wes McKinney (pandas creator) frames the danger line as whether you understand the code being generated: vibe coding produces code you don’t understand; agentic engineering produces code under structured oversight with comprehension intact. His practitioner framing from outside the Anthropic/Karpathy orbit adds credibility to the vibe-to-agentic transition narrative.
  • Agentic Engineering vs Vibe Coding: The New $190K Developer Job (Medium, 2026) — Labour market framing: agentic engineering is being positioned as a distinct job description at a $190K+ salary tier, distinct from traditional senior engineering. The implication: AI is not replacing senior engineers but is creating a premium tier for those who can orchestrate agents effectively.
  • [open-vs-closed-ecosystems] Kimi K2.7 Code (June 12, 1T params, 30% fewer thinking tokens than K2.6) and NVIDIA Nemotron 3 Ultra (June 4, 550B params, fully permissive) are new open-weight coding models that directly affect which tools practitioners have access to.
  • [vibe-coding-applications] Opsera’s productivity paradox data (42% AI code, 23.5% more incidents) is the most rigorous quantification yet of the adoption/quality gap; highly relevant to enterprise governance decisions.
  • [claude-teams] The trust/adoption gap (92% adoption, 29% trust) is an org-level metric; teams adopting at scale while trust remains low is the coordination problem this journal tracks.

Meta-observations #

  • Emerging pattern: The productivity paradox is now measured across multiple independent datasets (Opsera, Keyhole, DORA), not just theorised. The data is consistent: scoped task speed improves; system-level quality degrades. The implication for methodology is that agentic engineering (structured oversight, spec-first) is the evidence-based response to the paradox, not just a philosophical preference.
  • Keyword suggestion: “agentic engineering salary” or “AI coding job market 2026” — the labour market framing (McKinney, $190K tier article) is emerging as a distinct thread worth tracking.

2026-06-11 — Update #

Spec-Driven Infrastructure — GitHub Spec Kit at 84K Stars, Karpathy Declares Vibe Coding Over #

  • Vibe Coding vs Spec-Driven Development in 2026 (InterCode, 2026-06) — The framing is now clearly defined: vibe coding is prompt-driven (chat → code → iterate by prompting); spec-driven development treats the spec as the source of truth and code as compiled output. GitHub Spec Kit — an open-source spec-driven workflow toolkit — has accumulated 84,000 GitHub stars, supports 14 AI agent platforms, and has shipped 130 releases. This is the first major open-source infrastructure specifically for spec-driven workflows across multiple coding agents; it signals the community is treating spec-driven development as a durable pattern rather than a vendor-specific feature (contrast with AWS Kiro’s integrated approach). Andrej Karpathy, who coined “vibe coding” in February 2025, stated in June 2026 that “this era is ending” and that we are entering the age of agentic engineering — orchestrating agents against detailed specifications with human oversight.
  • [vibe-coding-applications] The spec-driven vs. vibe-coding distinction maps onto the enterprise adoption pattern — “vibe coding” for prototypes, spec-driven for production systems at scale.
  • [claude-teams] Spec-driven methodology (particularly the Martin Fowler “Encoding Team Standards” pattern) is the team-level application of what GitHub Spec Kit operationalises at the tooling level.

Meta-observations #

  • Quality signal: Karpathy declaring “vibe coding’s era is ending” is a meaningful pivot signal — he coined the term; his public distancing marks a cultural transition point worth tracking.

2026-06-11 — Gather #

Spec-Driven Tooling — AWS Kiro Adds Contradiction-Free Spec Verification #

  • AWS targets AI slop with new spec check in Kiro coding tool (GeekWire, 2026) — AWS is adding a feature to Kiro that mathematically proves software requirements are free of contradictions and gaps before any code is generated. The framing is explicit: this targets “AI slop” — code generated from contradictory or ambiguous specifications that fails at integration time. Alongside this: Parallel Task Execution now runs independent coding tasks concurrently, cutting implementation times for large projects by ~75%. Quick Plan mode lets developers skip step-by-step spec approval for well-understood features — a speed optimisation for repeat patterns. Kiro’s spec-first architecture is now the AWS response to the governance gap: if the spec is formally verified before code generation begins, the governance checkpoint moves upstream to the specification authoring stage.
  • Kiro vs Cursor (2026): The $20/mo Tool That Writes 0 Lines of Code First (MorphLLM, 2026) — Kiro’s positioning relative to Cursor: Kiro writes zero lines of code until a validated spec exists; Cursor starts with code generation immediately. The $20/month comparison (same price tier) makes the tradeoff explicit: structured spec-first workflow vs. immediate code generation with optional spec. AWS customer data: a 40-hour feature shipped in under 8 hours of human time when authored as a spec first. Kiro is now built on Amazon Bedrock with Claude and other foundation models as the underlying reasoning engine.

Market Scale — 92% US Developer Adoption, $4.7B Market #

  • Synergy Labs Blog: What Is Vibe Coding? Your 2026 Vibe Coding Guide (Synergy Labs, 2026) — AI coding tools market: $4.7 billion in 2026, growing at 38% CAGR. 92% of US developers use AI coding tools daily. 41% of global code is AI-generated. These three figures together define the transition point: AI coding is no longer an early-adopter practice — it is the default development environment for the overwhelming majority of US developers.

Learning Infrastructure — Google/Kaggle AI Agents Course #

  • Join the new AI Agents Vibe Coding Course from Google and Kaggle (Google, 2026-06) — Google and Kaggle’s free five-day AI Agents intensive course runs June 15–19, 2026. Focus: building production-ready AI agents using natural language workflows and hands-on coding projects. The Google/Kaggle infrastructure for this course has previously produced the largest cohorts of AI-tool learners (prior Kaggle GenAI courses drew 100,000+ participants). Free, structured, production-focused — the infrastructure for onboarding the next wave of developers into agentic engineering methodology at scale.
  • [vibe-coding-applications] AWS Kiro’s “contradiction-free spec verification” (formal methods applied to requirements before code generation) is the natural governance solution for the legacy modernisation use case: a 50-million-line Ruby codebase migration (Stripe + Fable 5, this cycle’s vibe-coding-applications entry) requires formally verified specifications to catch scope errors before 1,000 subagents execute.
  • [claude-expertise] Agent view in Claude Code (managing multiple concurrent sessions from one CLI) and Kiro’s Parallel Task Execution (concurrent independent coding tasks) are converging on the same agentic model from different entry points — Claude Code from the session management layer, Kiro from the specification layer.

Meta-observations #

  • Quality signal: The 92%/41% figures (US developer daily use / global code AI-generated) are market-size data that contextualise the governance gap research. If 41% of global code is AI-generated and only 36% of enterprises have centralised agentic governance (Berkeley Haas, 2026-05-27 gather), the ungoverned fraction of AI-generated code is already the largest single category of new code being deployed globally.
  • Emerging pattern: Spec-driven tooling is now the competitive battleground for agentic IDEs: GitHub Spec Kit (90K stars), AWS Kiro (contradiction-free verification), and multiple others have converged on spec-first as the differentiating architecture. The tooling competition is over; the debate is now which flavour of spec-first (lightweight/flexible vs. formally verified/rigid) fits which use case.
  • Keyword suggestion: "formal methods" "spec-driven development" AI agents verification 2026 — the formal verification of AI agent requirements (Kiro’s contradiction-check feature) is the most technically rigorous development in this space and is currently undertracked in practitioner coverage.

2026-06-04 — Gather #

Spec-Driven Development — GitHub Spec Kit Reaches 90K Stars #

  • Meet GitHub Spec-Kit: An Open Source Toolkit for Spec-Driven Development with AI Coding Agents (MarkTechPost, 2026-05-08) — GitHub Spec Kit (launched September 2025, now at 90,000+ stars) is the methodology tooling that operationalises spec-driven development: specifications, plans, and tasks as intermediate artifacts before code generation. Works with 30+ AI coding agents including Claude Code, GitHub Copilot, Gemini CLI, Cursor, Windsurf, and JetBrains Junie. Core pattern: describe what to build → refine through structured phases → let the agent implement. The tool converts the “agentic engineering” vocabulary shift (Karpathy) into a concrete workflow with shareable artifacts.
  • Diving Into Spec-Driven Development With GitHub Spec Kit (Microsoft Developer Blog) — Microsoft’s formal endorsement: spec-kit as the antidote to “piecemeal vibe coding” — the pattern where each session starts from context-free prompting with no persistent specification. The spec becomes the durable artifact that persists across sessions, models, and tools. Visual Studio Magazine framing: “Spec Kit Takes Off as Antidote to Piecemeal ‘Vibe Coding’” — the backlash against session-stateless prompting is now an official Microsoft development recommendation.
  • Dynamic Workflows Best Practices (Agent Update) — Crystallising practitioner guidance: (1) define clear scope and deliverables before launching — vague prompts like “Improve the app” cause subagents to fail to converge and waste tokens; (2) use selectively for tasks requiring genuine parallelism; (3) monitor via workflow history. The governance problem from the 2026-06-02 gather (who reviews 1,000 subagent outputs?) is addressed: structured scope declaration before launch is the primary mechanism.
  • [vibe-coding-applications] GitHub Spec Kit + Dynamic Workflows is the methodology pair for the Experian/TELUS-scale modernisation projects: Spec Kit provides the persistent specification and validation criteria; Dynamic Workflows provides the parallel execution infrastructure. Together they address both the governance gap and the context-window ceiling.
  • [claude-expertise] The Dynamic Workflows workflow keyword trigger config setting (captured this cycle’s claude-expertise gather) is the guardrail for the “vague prompt launches 1,000 subagents” failure mode identified in best practices coverage.

Meta-observations #

  • Emerging pattern: The methodology stack is crystallising: spec-first (Spec Kit) → parallel execution (Dynamic Workflows) → model routing (nine-factor framework, Jones) → review-at-scope (governance checkpoint). Each component addresses a different failure mode of naive agentic coding. The convergence of tools around this pattern suggests the methodology is no longer experimental.
  • Quality signal: 90,000+ GitHub stars for Spec Kit within ~8 months of launch is a strong adoption signal for a development methodology tool — not a product. Methodology adoption at this scale (comparable to major dev framework repositories) suggests the shift from session-stateless to spec-persistent is happening broadly.
  • Keyword suggestion: "spec-driven development" agent governance "scope declaration" checkpoint — the intersection of spec-first methodology with agentic governance (who approves the spec before 1,000 subagents execute it?) is the next methodological frontier and is currently undertracked.

2026-06-02 — Gather #

Dynamic Workflows — Agentic Engineering Infrastructure Ships #

  • Introducing dynamic workflows in Claude Code (Anthropic, 2026-05-28) — The first production infrastructure for agentic engineering at the scale Karpathy described theoretically. Claude writes a JavaScript orchestration script from a natural-language prompt; a background runtime executes up to 1,000 subagents (16 concurrent max) with checkpointing — interrupted runs resume mid-task. Reported use case: 750,000 lines of code rewritten in 6 days. The “agentic engineering” framing (human as supervisor of AI-executed work) is now operationally instantiated in tooling, not just vocabulary.
  • Claude Code Dynamic Workflows: A Deep Dive and Best Practices (Agent Update) — Good fits: codebase-wide bug hunts, security hardening passes, large migrations, profiler-guided optimization audits across entire codebases. Technical clarification: the orchestration script lives outside the conversation context window — task scale is no longer bounded by the 1M context limit. Subagents run in acceptEdits mode (file edits auto-approved); shell commands and web fetches can still prompt mid-run.

Enterprise — Concrete Throughput Numbers #

  • Agentic Engineering: The Complete Guide to AI-First Software Development Beyond Vibe Coding (NxCode, 2026) — Concrete production numbers from named enterprise deployments: Zapier 89% AI adoption across all engineering; Stripe Minions producing 1,000+ merged PRs per week; TELUS saved 500,000+ hours with 13,000 AI-generated solutions. These are the first published throughput benchmarks for agentic engineering at Fortune-500 scale — transforming the conversation from “what is agentic engineering” to “what does it produce at enterprise scale.”
  • [vibe-coding-applications] Dynamic Workflows at 1,000 subagents is the same tool that will drive the LegacyCodeBench-type large migration use cases tracked in vibe-coding-applications (92% COBOL accuracy, 750,000-line rewrites). The methodology question shifts from “can AI do this?” to “how do you govern 1,000 simultaneous agents?”
  • [claude-expertise] Dynamic Workflows is the operationalisation of the permission-friction quest answer: subagents in acceptEdits mode bypass per-operation approval for file edits, while shell commands remain subject to approval — a principled tiering of automation risk.
  • [ai-societal-impact] Stripe Minions (1,000+ merged PRs/week), Zapier 89% adoption, TELUS 500,000 hours saved — these are the enterprise-level productivity benchmarks that explain why the capital-labour substitution is accelerating. The “AI replacing workers” story is no longer speculative at these organisations.

Meta-observations #

  • Emerging theme: Dynamic Workflows removes context-window as the ceiling on agentic task scale. The new ceilings are: (1) governance — who reviews 1,000 subagent outputs?; (2) cost — 1,000 API calls per workflow at Opus 4.8 pricing is a non-trivial budget item; (3) debugging — what happens when the checkpoint/resume system encounters an inconsistent state? All three are unexplored in current coverage.
  • Quality signal: The 1,000-subagent cap (not unlimited) and 16-concurrent-agent limit suggest Anthropic has made deliberate capacity decisions. The specific numbers are worth tracking across releases — if the cap increases, it signals growing confidence in the checkpointing system.
  • Keyword suggestion: "dynamic workflows" checkpoint resume failure recovery governance audit — the failure modes and audit trail for large dynamic workflow runs are the unexplored technical angle.

2026-05-30 — Gather #

Agentic Engineering — Karpathy Declares “End of Vibe Coding” #

  • The End of Vibe Coding: Andrej Karpathy’s Shift to ‘Agentic Engineering’ (Buttondown / Verified) — Karpathy has declared vibe coding passé; the successor is “agentic engineering” — human as technical supervisor orchestrating autonomous agents that write, test, and deploy production-grade code. Developers who deeply understand architecture now have 10–100× leverage; novices generate broken code faster. The first practitioner-to-practitioner rebranding of the practice.

Gartner Hype Cycle — Agentic AI at Peak of Inflated Expectations #

  • 2026 Hype Cycle for Agentic AI (Gartner) — Agentic AI sits at the Peak of Inflated Expectations in the 2026 Hype Cycle; 40% of enterprise apps will embed task-specific agents by end-2026, up from <5% in 2025. Only 17% of organisations have deployed agents so far, but 60%+ expect to within two years — the most aggressive adoption curve of any emerging technology in this year’s survey.
  • Gartner Predicts 40% of Enterprise Apps Will Feature Task-Specific AI Agents by 2026 (Gartner, 2025-08-26) — Original prediction confirming source; long-term projection of agentic AI driving ~30% of enterprise application software revenue by 2035 ($450B+, up from 2% in 2025). The revenue figure is the clearest signal that this is now infrastructure, not a feature.
  • [vibe-coding-applications] The Gartner 40% enterprise app figure is the adoption-side number; the question of whether those deployments are governed is separate and tracked in vibe-coding-applications (comprehension debt, governance gaps).
  • [ai-societal-impact] Karpathy’s agentic engineering framing explicitly assigns different productivity multipliers to expert vs. novice — “technical mastery is even more of a multiplier than before.” This is the skill-gap story from the societal angle.

Meta-observations #

  • Emerging pattern: The vibe-coding label is being retired by its own most-cited practitioner. “Agentic engineering” is Karpathy’s deliberate rebranding to elevate the practice from casual prototyping to disciplined software supervision. Expect this terminology to propagate through the practitioner community within months given his Anthropic role.
  • Quality signal: The Gartner Hype Cycle placement at Peak of Inflated Expectations is the canonical signal that the enterprise adoption curve is real but a correction is coming — governance, reliability, and oversight tooling are the next bottlenecks.

2026-05-27 — Gather #

Academic Institutionalisation — VibeX 2026 #

  • VibeX 2026 — 1st International Workshop on Vibe Coding (EASE 2026) (EASE 2026) — The first dedicated academic workshop on vibe coding, co-located with the EASE software engineering conference. Signals the concept has crossed from practitioner discourse into formal research — the stage at which vocabulary stabilises and empirical measurement frameworks get established.

Karpathy — From Coding to Second Brain #

  • Andrej Karpathy joins Anthropic (Fortune, 2026-05-19) — Karpathy joined Anthropic’s pretraining team in May 2026. Institutionally significant: the practitioner most cited in the vibe-coding-to-agentic-engineering transition is now inside the organisation building the primary coding agent. Expect pretraining research to incorporate his agentic workflow experience.
  • Karpathy stopped using AI to write code — using it to build a second brain (Medium / Neural Notions) — Karpathy’s next evolution: shifted AI use from code generation to knowledge organisation — building interlinked wikis from raw research. Vibe coding now looks like the midpoint; the endpoint is AI as epistemic infrastructure rather than coding assistant.

Governance Gap — Enterprise Numbers #

  • Governing the Agentic Enterprise (California Management Review, Berkeley Haas, 2026-03) — Only 36% of organisations have centralised agentic AI governance. The governance gap is now the defining structural problem of enterprise AI adoption — not capability gaps.
  • Agentic AI Enterprise Adoption 2026: 72% Production Proven (Agentic AI Institute) — 72% of enterprises have agentic AI in production; 60% governance gap; only 12% use a centralised platform for sprawl control. Adoption/governance asymmetry confirmed from a second independent data source.
  • Multi-Agent Orchestration for Developers in 2026 (Scopir) — 57% of organisations deploy multi-step agent workflows in production; coding sessions now average 23 minutes vs. 4 minutes a year ago. The extended session length is a proxy for increasing complexity of delegated tasks.

The AI Engineering Stack #

  • The AI Engineering Stack — Gergely Orosz and Chip Huyen (Pragmatic Engineer) — Collaborative piece defining the AI engineering stack: most AI engineering roles involve building on top of APIs, not training models. Establishes the new practitioner category distinct from ML engineering.
  • The Code Agent Orchestra (Addy Osmani) — Orchestration patterns: central planner + specialist workers; MCP as the standard interface with 5,000+ registered servers. Osmani frames multi-agent coding as a conductor problem — human value is orchestration strategy, not implementation.
  • From IDEs to AI Agents — Steve Yegge and Gergely Orosz (Pragmatic Engineer) — Yegge/Orosz on the shift from IDE-centric to agent-centric development. Yegge’s framing of the transition is structurally different from Karpathy’s: focused on tooling architecture rather than individual workflow change.
  • [vibe-coding-applications] The governance gap (36% with centralised governance, Berkeley Haas) is the enterprise condition that produces comprehension debt accumulation — unmanaged agents generate code that nobody audits, which is the mechanism Osmani and ByteIota measure empirically.
  • [claude-expertise] Karpathy joining Anthropic’s pretraining team is the organisational signal that practitioner agentic workflow knowledge is entering the pretraining research pipeline directly.
  • [ai-societal-impact] “Token maximising” behaviour at Meta/Microsoft (engineers gaming productivity metrics based on AI output counts) is the micro-level expression of the societal-impact concern: AI-attributable cost savings for shareholders without genuine productivity gains for workers.

Meta-observations #

  • Emerging pattern: Three independent tracks (VibeX academic workshop; Berkeley Haas/Agentic AI Institute governance gap research; Osmani orchestration patterns) are converging on the same conclusion: vibe coding as individual practice is now a mainstream assumption; the frontier question is governance and orchestration at enterprise scale.
  • Quality signal: Karpathy’s “second brain” evolution is the clearest signal that the vibe-coding narrative has reached an inflection — the field’s most cited practitioner has moved past code generation entirely. His move to Anthropic pretraining is the institutionalisation of that inflection.
  • Author to watch: Addy Osmani — Google engineering lead, authored both the comprehension debt paper (O’Reilly Radar) and the Code Agent Orchestra (personal blog) in the same gather window. Two high-quality independent pieces; worth adding to watch_authors.

2026-05-22 — Gather #

Karpathy — Sequoia Ascent: Floor vs Ceiling #

  • Sequoia Ascent 2026 Summary (Karpathy, bearblog) — Karpathy’s Sequoia Ascent keynote summary. Clearest articulation of the split: vibe coding “raises the floor” (anyone can prototype); agentic engineering “raises the ceiling” (coordinating fallible agents while maintaining quality). The developer role has shifted from code writer to agent supervisor — “macro actions” (implement feature, refactor system) replace line-by-line authorship. The most quotable line: “you can outsource your thinking, but you can’t outsource your understanding.” Comprehension becomes the bottleneck for effective direction as delegation scales.
  • Andrej Karpathy on the Evolution from Vibe Coding to Agentic Engineering (Frank’s World of Data Science) — Useful synthesis of Karpathy’s December 2025 inflection point framing: models started producing chunks of code that “just worked”; the last time he manually corrected output was December. The transition isn’t gradual adoption — it’s an inflection point after which the workflow model fundamentally changed.

Willison — Convergence is Uncomfortable #

  • Vibe Coding and Agentic Engineering Are Getting Closer Than I’d Like (Simon Willison, 2026-05-06) — Willison’s “disturbing realization”: he now skips code review for standard implementations he trusts the model to get right — a practice he would have previously called vibe coding. The convergence: when you stop reviewing AI-generated code for certain task types, the distinction between vibe and agentic engineering collapses functionally. His resolution: treating AI agents like trusted teams at a larger company whose work you use without examining every line. The risk he names: “normalisation of deviance” — repeated success builds false confidence. Importantly, he maintains the ethical distinction: vibe coding for other people’s systems remains “grossly irresponsible”; the convergence is in his own personal tooling.

Formal Taxonomy — Vibe vs Agentic Coding #

  • Vibe Coding vs. Agentic Coding: Fundamentals and Practical Implications of Agentic AI (arXiv, 2026-05) — Academic taxonomy: vibe coding = “intuitive, human-in-the-loop interaction through prompt-based conversational workflows”; agentic coding = “autonomous software development through goal-driven agents capable of planning, executing, testing, and iterating.” The paper’s core argument: the binary is wrong — successful AI software engineering requires harmonising both, not choosing. Proposes a unified human-centred lifecycle with hybrid architectures. The vocabulary this paper provides (vibe vs agentic as axes, not binary categories) is now entering practitioner discourse.

Spec-Driven Development — Mainstream Tooling Wave #

  • Spec-Driven Development with Coding Agents (DeepLearning.AI) — Dedicated SDD course from DeepLearning.AI signals methodology has crossed from experimental to mainstream. Every major AI coding tool — GitHub Spec Kit, AWS Kiro, Claude Code, Cursor — now ships its own SDD implementation.
  • Agentic Coding at Enterprise Scale Demands Spec-Driven Development (VentureBeat) — Enterprise adoption driver: AWS Kiro documents real customer cases where 40-hour features shipped in under 8 hours of human time when authored as specs first. GitHub reports order-of-magnitude reduction in “regenerate from scratch” cycles with Spec Kit. SDD is no longer a best practice aspiration — it’s the governance mechanism enterprise teams are adopting to manage AI code drift.
  • [vibe-coding-applications] Karpathy’s “comprehension is the bottleneck” frames the O’Reilly/Osmani comprehension debt finding as a structural consequence of delegation at scale, not a failure of individual discipline.
  • [claude-expertise] Willison’s normalisation-of-deviance risk applies directly to teams using Claude Code without review for standard patterns — the security vulnerabilities found this week (Check Point, TrustFall) are exactly the failure mode he anticipates.
  • [ai-societal-impact] The floor/ceiling framing maps directly onto the workforce impact story: vibe coding raising the floor creates citizen developers; agentic engineering maintaining the ceiling requires experienced practitioners — the gap between the two is the reskilling problem.

Meta-observations #

  • Emerging pattern: Three independent sources (Karpathy, Willison, arXiv paper) are converging on the same structural claim: the vibe/agentic distinction was a useful heuristic but is collapsing as model quality increases and trust extends. The framing is shifting from “which paradigm” to “when does each apply.”
  • Quality signal: Karpathy’s “you can outsource thinking but not understanding” is the cleanest articulation of what human value remains in an agentic workflow. Worth tracking as this formulation enters practitioner vocabulary.
  • Keyword suggestion: "agentic engineering" governance enterprise 2026 — the enterprise adoption of SDD as a governance mechanism is the next wave; separate from the practitioner-technique discourse.

2026-05-19 — Gather #

Karpathy — No Code Since December, Now Directing Agents #

  • Karpathy Hasn’t Written Code Since December — He Just Directs AI Agents Now (htek.dev) — Karpathy’s workflow inversion: no manual code since December 2025, now directing fleets of up to 20 parallel agents. The 80/20 ratio of human-to-AI code authorship has inverted. The Autoresearch project — 700 experiments in 2 days from one markdown prompt — is cited as the clearest demonstration of what directing agents at scale looks like.
  • Andrej Karpathy Has Renamed Vibe Coding — What Engineering Leaders Need to Do (SD Times) — Karpathy’s reframing: moving “vibe coding” as a pejorative to “agentic engineering” as a discipline requiring deliberate investment in process and tooling. Engineering leaders who dismiss vibe coding as undisciplined are now being asked to take agentic engineering seriously as a structured practice — they’re the same thing with different governance expectations.

Pragmatic Engineer — Definitive Practitioner Survey #

  • AI Tooling for Software Engineers in 2026 (Pragmatic Engineer) — Survey of 900+ engineers: Claude Code now leads as the most-used AI coding tool, overtaking Copilot and Cursor. 95% use AI tools weekly; 55% regularly use agents. The most comprehensive practitioner survey of the year — benchmark data for tracking adoption velocity.
  • The Impact of AI on Software Engineers in 2026: Key Trends (Pragmatic Engineer) — 75% of engineers use AI for half or more of their work. Agent users are twice as excited about AI as non-users. Anthropic models dominate coding by a wide margin over competitors. Senior engineers (staff+) lead agent adoption at 63.5%.
  • How Claude Code Is Built (Pragmatic Engineer) — Deep technical dive into Claude Code’s architecture and design decisions from Orosz’s conversations with the Anthropic team. Unusually substantive inside view; covers why it’s terminal-based, how plan mode works, and the decision-making behind the agentic UX.

Spec-Driven Development — Now Formalised #

  • Spec-Driven Development: From Code to Contract in the Age of AI Coding Assistants (arXiv) — Academic formalisation of SDD as a response to AI-generated code drift. Documents vulnerability rates of 9.8%–42.1% across benchmarks and argues for executable specifications as the control mechanism. The paper that gives practitioners the vocabulary to explain why “just vibe it” produces technically risky codebases.
  • Diving Into Spec-Driven Development with GitHub Spec Kit (Microsoft Developer Blog) — Hands-on walkthrough of GitHub’s Spec Kit CLI: spec-first workflow, reported order-of-magnitude reduction in “regenerate from scratch” cycles. Microsoft is investing in the spec-driven approach as the governance layer for AI coding in enterprise contexts.

Willison — The Agentic Engineering Pattern Library #

  • Agentic Engineering Patterns: Linear Walkthroughs (Simon Willison) — The “linear walkthrough” pattern: using a coding agent to generate a structured explanation of vibe-coded code you don’t fully understand. A practical technique for managing comprehension debt after the fact — pairs naturally with Osmani’s comprehension debt framing.
  • Agentic Engineering Patterns: Writing Code Is Cheap Now (Simon Willison) — Writing is nearly free; the bottleneck shifts to review, intent specification, and maintaining understanding. Inverting the economics of software development changes what skills matter — not less important to be an engineer, differently important.
  • Highlights from My Conversation About Agentic Engineering on Lenny’s Podcast (Simon Willison, 2026-04-02) — Willison’s evolving views on responsible agentic engineering, when vibe coding is acceptable, and his own workflow practices. Useful as a practitioner’s own periodic synthesis.

Multi-Agent Production — What Survived #

  • Multi-Agent in Production 2026: 3 Patterns That Survived (NiteAgent) — Post-mortem: agent-flow (assembly line), orchestration (hub-and-spoke), and bounded collaboration (controlled peer mesh) survived in production. Peer-collaboration systems failed universally. The practical design guidance for anyone building multi-agent systems now — not theoretical patterns but empirically validated ones.

Context Engineering — The New Skill #

  • Context Engineering Best Practices for AI-Powered Dev Teams (2026) (Packmind) — The context lifecycle: create → distribute → maintain → update → measure. Covers CLAUDE.md-style files as team-level context artefacts, context drift as conventions evolve, and measuring context effectiveness. Practical operationalisation of what “context engineering” means at team scale.
  • [claude-expertise] The Pragmatic Engineer survey establishes Claude Code as the leading AI coding tool — a direct data point for the claude-expertise topic’s coverage of adoption patterns.
  • [vibe-coding-applications] The arXiv SDD paper (9.8%–42.1% vulnerability rates) provides the formal evidence base for the enterprise risk concerns surfacing in the applications journal.
  • [ai-societal-impact] Karpathy directing 20 parallel agents is the most vivid current image of what the “anticipatory layoffs” in ai-societal-impact are anticipating — the skill compression is now documented and named.

Meta-observations #

  • Quality signal: The Pragmatic Engineer survey data (900+ respondents, Claude Code #1) is the most credible adoption measurement available. It supersedes previous qualitative claims about tool leadership.
  • Emerging pattern: The “agentic engineering patterns” genre is maturing — Willison’s guides are the most systematic attempt to build a practitioner pattern library. Watch for this to become a formal curriculum in 2026 (see the DeepLearning.AI SDD course).
  • Keyword suggestion: "agent-flow" OR "orchestration pattern" multi-agent production — the production pattern vocabulary is stabilising; these specific terms now have empirical backing.

2026-05-18 — Gather #

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-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.
  • [vibe-coding-applications] 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.

2026-05-14 — Gather #

Governance Layer Matures #

  • VibeX 2026 — 1st International Workshop on Vibe Coding and Vibe Researching (EASE 2026) — First dedicated academic workshop on vibe coding, co-located with the Empirical Software Engineering & Measurement conference. Topics: empirical studies of AI-assisted development practices, productivity measurement, software quality under vibe coding, and the human-AI collaboration loop. Signal: vibe coding has moved from blog-post discourse into empirical research territory.
  • Introducing the Agent Governance Toolkit: Open-source runtime security for AI agents (Microsoft Open Source) — Microsoft releases an open-source runtime security framework for AI coding agents. Intercepts agent actions in real time, applies policy rules, and produces an immutable audit trail. Positions governance not as a policy document but as a technical layer agents must pass through. Practical for multi-agent pipelines where individual agent behaviour needs to be auditable.
  • 6 Multi-Agent Orchestration Patterns for Production (Beam.ai) — Production-validated taxonomy: orchestrator-worker (known task decomposition), sequential pipeline (fixed linear steps), fan-out/fan-in (independent parallel work), multi-agent debate (quality verification), dynamic handoff (unpredictable routing), adaptive planning (open-ended problems). Model tiering is now standard: cheap/fast model (Haiku 4.5) for triage/routing agents, capable model (Sonnet 4.6) for reasoning agents.

Context Engineering as Practice #

  • Effective context engineering for AI agents (Anthropic Engineering) — Anthropic’s own framing: context engineering = curating what the model sees before inference. “Just in time” context: agents maintain lightweight identifiers (file paths, stored queries, web links) and load data into context at runtime via tools rather than pre-loading everything. 57% of enterprises run agents in production; quality remains the top barrier, and the problem is context governance, not code generation.
  • AGENTS.md Complete Guide for Engineering Teams (BuildBetter) — AGENTS.md has emerged as the de facto universal agent instruction format: read natively by Claude Code, Codex CLI, Cursor, Aider, Devin, GitHub Copilot, Gemini CLI, Windsurf, and Amazon Q. The cross-tool standardisation means a single AGENTS.md file functions across the IDE landscape without modification.
  • 2026 Agentic Coding Trends Report (Anthropic) — Anthropic’s quantified view: coding agent session duration grew from 4 min average to 23 min; 78% of sessions now involve multi-file edits; 57% of orgs run agents in production. The session-duration jump suggests agents are no longer being used for one-shot code generation but for sustained, multi-step workflows.

Karpathy — Second Brain Shift #

  • Andrej Karpathy Stopped Using AI to Write Code (Neural Notions, Medium) — Karpathy describes a working system beyond code generation: dumps raw research materials into a folder, points an LLM at it, and the LLM builds and maintains an interlinked wiki from scratch — writing articles, creating backlinks between related ideas, categorising concepts. Frame: the most interesting use of LLMs is knowledge synthesis, not code authorship. Note: Medium source but reporting on a direct Karpathy description.
  • [claude-expertise] Anthropic’s own context engineering post directly operationalises what agentic engineering means in their toolchain — it’s the Claude Code runtime design document in public form.
  • [vibe-coding-applications] AGENTS.md cross-tool standardisation matters for enterprise: a single governance artefact now works across tool choices, removing one obstacle to setting company-wide AI coding policy.
  • [claude-expertise] Code w/ Claude 2026 Outcomes feature is a direct implementation of multi-agent debate pattern — a grader agent evaluates the task agent’s output without seeing its reasoning.

Meta-observations #

  • Emerging pattern: Governance is now a technical discipline, not just a policy one. Microsoft’s toolkit, Anthropic’s context engineering post, and the OWASP Agentic Top 10 all treat governance as runtime infrastructure. Next gather: look for vendor certification or compliance attestation products in this space.
  • Keyword suggestion: "AGENTS.md" engineering teams — the cross-tool standardisation story is early and under-covered.

2026-05-09 — Gather #

Karpathy’s Reframing — “Vibe Coding is Passé” #

  • Vibe coding is passé. Karpathy has a new name for the future of software. (The New Stack) — Karpathy formally retires his own term. “Today, programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny.” The replacement vocabulary: “agentic engineering.” Core distinction: vibe coding = reactive (human calls, AI responds linearly); agentic engineering = proactive (agents plan, execute, verify, and iterate with limited human input between steps).
  • Andrej Karpathy Says AI Coding Is Moving From Vibe Prompts to Agent Workflows (AIntelligenceHub, May 2026) — Karpathy at AI Ascent 2026: 80% of his code is now AI-generated. “It’s a bit hard on the ego but too useful to abandon.” Key framing: verifiability is the limiting factor — agentic automation accelerates in domains where outputs are easily verifiable (code, with test suites) and stalls where they are not (strategy, design — no ground truth).
  • From vibes to engineering: How AI agents outgrew their own terminology (The New Stack) — The New Stack’s analysis: “agentic engineering” is now in active use across Anthropic, Google, and community practitioners. Adopted faster than “vibe coding” because it describes a discipline rather than a feeling.
  • Agentic Engineering (Addy Osmani) — Osmani’s definition: agentic engineering is oversight work, not code authorship. The human role is: set scope, define verification criteria, review agent outputs, steer agent direction. Code volume is incidental; maintaining system coherence is the core skill.

Tool Market — Consolidation Signals #

  • AI Coding Agents 2026: Claude Code vs Cursor vs Windsurf vs Copilot (Lushbinary) — Market structure: Cursor crossed $1B ARR; GitHub Copilot has 4.7M paid subscribers and 90% Fortune 100 adoption; Windsurf acquired by Cognition for $250M (Google separately paid $2.4B for Windsurf’s founding team access). New entrant: Kiro (Amazon AWS), positioning in the agentic workflow tier against Cursor. Enterprise IDE choices are narrowing to 3–4 platforms.
  • Coding Agents Comparison: Cursor, Claude Code, GitHub Copilot, and more (Artificial Analysis) — Independent benchmark tracking: Claude Code leads on reasoning quality; Cursor leads on UX polish and community; Windsurf leads on value-for-money at the $15/month tier. Every tool is now racing toward background agents and autonomous PR generation — the boundary between IDE tool and autonomous agent is dissolving.
  • [claude-expertise] Code w/ Claude 2026 Managed Agents announcements (Dreaming, Outcomes, Multiagent) are Anthropic’s own concrete implementation of the agentic engineering patterns Karpathy is articulating — Dreaming in particular directly addresses Karpathy’s verifiability constraint by adding a memory-review loop.
  • [vibe-coding-applications] Cursor’s $1B ARR and Windsurf’s acquisition signal that the enterprise tool market is consolidating — the governance question (which tool, which model, which data policy) is becoming a procurement decision at scale.

Meta-observations #

  • Emerging pattern: Karpathy retiring “vibe coding” is the clearest vocabulary signal of 2026 — the term’s progenitor has moved on. Tracking which publications adopt “agentic engineering” vs continue using “vibe coding” will reveal which audiences are lagging the practitioner frontier.
  • Quality signal: Addy Osmani’s framing (“oversight work, not code authorship”) is the most precise definition of the human role in agentic engineering to date — useful as a reference for enterprise training and role definition.
  • Keyword suggestion: "agentic engineering" site:thenewstack.io OR site:martinfowler.com OR site:addyosmani.com — high-signal sources converging on the new vocabulary.
  • Gap: No empirical study comparing productivity gains vs comprehension loss at the same organisation. All productivity claims remain practitioner-asserted; all comprehension debt claims remain qualitative.

2026-05-06 — Gather #

Context Engineering — The Real Bottleneck #

  • Context Engineering for Coding Agents (Martin Fowler) — Martin Fowler frames context engineering as the architectural discipline replacing prompt engineering: MCP as Select, CLAUDE.md as config-layer context, structured specs as dynamic injection. The piece gives the term architectural legitimacy beyond the practitioner conversation.
  • Context is AI coding’s real bottleneck in 2026 (The New Stack) — 57% of enterprises run coding agents in production; quality remains the top barrier. Anthropic’s 2026 Agentic Coding Trends Report names context engineering as the most important skill shift. Among 10,000+ employee organisations, “managing context at scale” is the leading quality challenge.
  • State of AI Engineering (Datadog) — Industry survey: context gap is what determines how much of the theoretical productivity gain teams actually capture. Model capability is no longer the binding constraint for most production use cases.

Agentic Engineering — Patterns and Vocabulary #

  • [claude-expertise] Claude Code’s post-regression remediation (harness ablation gating, internal dogfooding) is directly relevant to the “agentic governance” keyword — product-layer quality control is the enterprise adoption gating factor.
  • [vibe-coding-applications] The security governance story (1,000 PRs/week × 1% vulnerability rate) connects directly to enterprise adoption patterns and citizen developer shadow IT.

Meta-observations #

  • Emerging theme: Context engineering is now the dominant professional framing for AI coding skill — it has displaced both “prompt engineering” and “spec-driven development” as the vocabulary of serious practitioners. Martin Fowler’s endorsement is the clearest signal it has crossed into architectural mainstream.
  • Keyword suggestion: "context engineering" coding agent — now the highest-signal term for technique-focused content.
  • Keyword suggestion: "PEV loop" OR "plan execute verify" agent — the emerging agentic workflow vocabulary.
  • Gap: Still no rigorous benchmark comparing context-engineered vs unstructured agentic coding at equivalent task difficulty. The productivity claims remain practitioner-asserted, not empirically validated.

2026-05-02 — Gather #

Karpathy’s Agentic Engineering Manifesto (May 2026) #

  • Andrej Karpathy on the Evolution from Vibe Coding to Agentic Engineering (Frank’s World, May 1 2026) — Karpathy formalises his “Software 3.0” paradigm: programming embedded in sophisticated LLM prompts. Core insight: verifiability is the limiting factor — automation accelerates in domains where outputs are easily verifiable, creating “jagged” results (models excel at some tasks while failing at seemingly simpler ones). Maintains deep understanding of underlying mechanics is non-negotiable; engineers must be able to verify what agents produce.
  • Anthropic’s 2026 Agentic Coding Report (VentureBeat) — Anthropic’s report emphasises: agentic engineering must embed security from day one. Building security into the harness — not bolting it on later — is non-negotiable. Positions this as architectural discipline, not tooling.

Real-World Production Numbers #

  • The state of vibe coding in 2026: Adoption won, now what? (Hashnode) — Concrete adoption data: Stripe Minions produces 1,000+ merged PRs per week; TELUS saved 500,000+ hours with 13,000 AI solutions; Zapier hit 89% AI adoption across the entire organisation. These are the first industry-scale adoption metrics from production deployments, not pilots.

Spec Kit Agents — Academic Validation #

  • [vibe-coding-applications] Stripe’s 1,000+ PRs/week and TELUS’s 500,000 hours saved are the enterprise-scale benchmarks that the applications journal’s case studies (Grid Dynamics, Codurance) are converging toward — the velocity numbers are consistent across sectors.
  • [claude-expertise] Karpathy’s “verifiability as limiting factor” maps directly to Claude Code hooks — PreToolUse hooks and Verifier Agent patterns are the engineering response to the verification problem he identifies.
  • [ai-societal-impact] Zapier’s 89% organisation-wide AI adoption is the starkest data point yet on the speed of workplace transformation — faster than any prior enterprise software transition.

Meta-observations #

  • Emerging theme: Verifiability as the structural constraint on agentic automation — Karpathy’s framing is the most precise theoretical explanation for why agentic engineering produces “jagged” results. Tasks where correctness is easy to check (tests pass/fail, compilation succeeds) automate cleanly; tasks requiring human judgment resist automation structurally.
  • Emerging pattern: Production-scale adoption data is now arriving: Stripe, TELUS, Zapier numbers are the first industry-scale empirical evidence. The anecdote-to-data transition is complete for early adopters.
  • Quality signal: arXiv validation of Spec Kit Agents is the first peer-reviewed academic work on the Coordinator/Implementor/Verifier architecture — elevates it from practitioner pattern to research-validated approach.
  • Keyword suggestion: “verifiability constraint” — Karpathy’s concept that automation success correlates with output checkability; worth tracking as this framing propagates.
  • Source to watch: Hashnode’s “state of vibe coding” annual piece — first edition to contain real production metrics rather than projections.

2026-04-25 — Gather #

Four Pillars Framework (Red Hat) #

  • Vibes, specs, skills, and agents: The four pillars of AI coding (Red Hat Developer, Mar 30 2026) — Authoritative four-part taxonomy: Vibes (natural-language intent, exploratory), Specs (formal structured requirements), Skills (reusable modular automation), Agents (autonomous multi-step execution). Positions each as complementary, not competing. Red Hat’s weight gives this enterprise legitimacy.

Agentic Engineering Maturation #

Spec-Driven Development vs Vibe Coding (Formal Comparison) #

Multi-Agent Architecture (SDD Formalised) #

  • Intent implements a multi-agent paradigm (VentureBeat) — Structured agent model now formalised: Coordinator Agent (analyses codebase, drafts spec), Implementor Agents (execute tasks in parallel against spec), Verifier Agent (checks consistency and correctness). Three-role architecture becoming the emerging standard.
  • [vibe-coding-applications] Red Hat’s four-pillar framework maps directly to enterprise adoption patterns: Skills and Specs are the governance layer enterprises are building on top of Vibes-era tooling.
  • [claude-expertise] Claude Managed Agents (Anthropic’s new platform feature) is the infrastructure enabling the Coordinator/Implementor/Verifier three-agent architecture described in VentureBeat.
  • [vibe-coding-applications] VentureBeat and CIO articles converge on the same dual-track conclusion from different angles — the enterprise and methodology journals are reinforcing each other this cycle.
  • [open-vs-closed-ecosystems] Red Hat (IBM subsidiary) publishing a four-pillar AI coding framework suggests enterprise Linux/cloud vendors are now actively shaping vibe-coding methodology, not just toolmakers and AI labs.

Meta-observations #

  • Emerging theme: Spec-Driven Development has become an enterprise governance mandate, not just a methodology option. VentureBeat, CIO, Augment Code, and DevLand all frame SDD as required for production — the professional standard is crystallising.
  • Emerging pattern: The Coordinator/Implementor/Verifier three-role agent architecture is the first structural attempt to encode governance into the agent pipeline itself. This is beyond workflow patterns — it’s agentic governance by design.
  • Emerging pattern: Red Hat’s four-pillar framework (Vibes/Specs/Skills/Agents) is the most credible enterprise-facing taxonomy to date. Prior taxonomies came from startups or individual practitioners; Red Hat carries enterprise validation weight.
  • Keyword suggestion: “Coordinator Agent” / “Implementor Agent” / “Verifier Agent” — the three-role multi-agent pattern is worth tracking as a formal architecture term.
  • Keyword suggestion: “agentic governance” — governance embedded into agent pipeline design, distinct from human oversight governance.
  • Source to watch: developers.redhat.com — Red Hat Developer portal publishing framework-level AI coding analysis with enterprise weight. Add to preferred sources.
  • Source to watch: augmentcode.com — producing substantive methodology comparisons, not product marketing. High signal-to-noise.
  • Noise pattern: “End of vibe coding” framing is proliferating in titles — distinguish between substantive analysis (DevLand conference talk, VentureBeat) and clickbait using the phrase for SEO. Title filter alone insufficient; require substance in body.

2026-04-10 — Gather #

Karpathy + Agentic Engineering (Continued Maturation) #

Spec-Driven Development (Tool Consolidation) #

Multi-Agent Orchestration (Framework Wars) #

Pragmatic Engineer (Gergely Orosz) #

  • [claude-expertise] The Agent Skills standard crossing Claude Code → Codex → Gemini CLI is the tooling-layer manifestation of the methodology convergence around spec-driven + agentic engineering.
  • [vibe-coding-applications] “Supervisor class” framing in Fortune connects practitioner methodology directly to enterprise labour-market narrative.
  • [ai-societal-impact] Agentic engineering’s “99% orchestration” framing is the mechanism behind BCG’s “reshape not replace” — developer roles change but don’t vanish.
  • [open-vs-closed-ecosystems] Microsoft Agent Framework (merged AutoGen+Semantic Kernel) is a closed-source-but-standards-friendly framework occupying the hybrid middle; contrast with LangGraph (open) and Claude Agent SDK (closed-but-documented).

Meta-observations #

  • Emerging theme: Agentic engineering has moved beyond Karpathy’s reframe into industry-wide terminology. April 2026 dated articles use “agentic engineering” without scare quotes. The linguistic transition is complete.
  • Emerging theme: A contrarian counter-narrative is forming around SDD. “Waterfall in Markdown” (Rick’s Cafe) and ThoughtWorks radar “Assess” rating are early warnings that the spec-first paradigm may over-index on up-front design. Worth tracking whether this becomes a substantive critique or gets drowned out.
  • Emerging pattern: Framework consolidation. Microsoft Agent Framework (merging AutoGen + Semantic Kernel) suggests the multi-agent-framework space is converging, not fragmenting. Expect LangGraph / CrewAI to absorb smaller frameworks over 2026.
  • Keyword suggestion: “supervisor class” — Fortune’s framing for the new developer role. Bridges vibe-coding methodology to labour-market analysis.
  • Keyword suggestion: “auto-research” — Karpathy’s extension of agentic engineering beyond code into research loops. Likely to proliferate.
  • Keyword suggestion: “waterfall in markdown” / “SDD critique” — the contrarian frame; worth tracking whether it gains traction.
  • Source to watch: Rick’s Cafe AI — producing rare contrarian analysis in a hype-saturated space.
  • Source to watch: The AI Agent Index — emerging as a neutral orchestration-landscape reference.
  • Quality signal: The Pragmatic Engineer continues producing high-signal practitioner interviews (DHH, Steve Yegge, Boris Cherny). Primary-source interview content remains the highest-value format in this space.
  • Gap: Still no good benchmark comparing SDD outcomes to unstructured AI coding at equivalent task difficulty. The “SDD is better” claim is widely asserted but underdocumented. METR’s “19% slower with AI” finding is the only rigorous counter-benchmark, and it wasn’t SDD-specific.
  • Noise pattern: Vendor-sponsored “6 Best X Tools 2026” listicles continue to dominate the keyword surface. The exclude_terms filter is effective; augment/augmentcode-authored content is high-volume but lower-signal (though not worthless).
  • Gap: Very little on technique (how to prompt effectively, how to structure projects for AI). Mostly tool comparison. May need different keywords to find technique-focused content.

2026-04-05 — Gather #

The Term Shift: “Vibe Coding” → “Agentic Engineering” #

Spec-Driven Development (Formalised) #

Multi-Agent Orchestration (Architecture) #

Industry Data & Adoption #

Prompt-Driven Development (Academic & Industry) #

Vibe Coding in Practice #

  • [claude-expertise] Boris Cherny’s 5-parallel-terminal workflow + Gergely Orosz’s Claude Code survey are direct Claude-specific corroboration of the multi-agent Tier-1/Tier-2 framing.
  • [claude-expertise] The METR “19% slower” finding and DORA bug-rate numbers are the cautionary counterweights to optimistic Claude Code tips content.
  • [vibe-coding-applications] Stripe’s 1,000 PRs/week + 57% enterprise adoption are concrete application data points.
  • [ai-societal-impact] METR + DORA findings (AI makes devs slower, bugs up) are the empirical basis for sentiment skepticism.
  • [open-vs-closed-ecosystems] Claude Code dominance in Pragmatic Engineer survey is a closed-ecosystem win worth tracking.

Meta-observations #

  • Emerging theme: The term “vibe coding” is being actively retired by its coiner in favour of “agentic engineering”. Worth watching whether industry follows Karpathy or keeps the viral term.
  • Emerging theme: Spec-Driven Development has graduated from concept to tooled-up category with GitHub Spec Kit (72k stars), AWS Kiro (IDE), Tessl. This is the structural antidote to unstructured vibe coding.
  • Emerging pattern: Three-tier orchestration taxonomy (in-process / local / cloud async) is becoming a shared mental model — cite Addy Osmani as canonical.
  • Emerging pattern: Counter-narrative is gathering empirical backing — METR 19% slowdown, DORA 9% more bugs, 154% larger PRs. Previously only anecdotal.
  • Keyword suggestion: “agentic engineering” — new umbrella term, worth adding as keyword.
  • Keyword suggestion: “spec-driven development” OR “spec coding” — now concrete enough to track independently of vibe coding.
  • Keyword suggestion: “GitHub Spec Kit” / “AWS Kiro” / “Tessl” — specific tools warranting their own queries.
  • Author to watch: Addy Osmani (addyosmani.com) — producing the most cited architectural analysis this cycle.
  • Author to watch: Mike Mason (mikemason.ca) — thoughtful essays on orchestration philosophy.
  • Source to watch: martinfowler.com — long-form authoritative analysis (Spec-Driven Development article).
  • Source to watch: resources.anthropic.com — official Agentic Coding Trends reports.
  • Source to watch: agentic.hamburg — conference proceedings from Agentic Conf Hamburg.
  • Quality signal: Pragmatic Engineer (Gergely Orosz) publishes survey data rare in this space — treat as high-signal primary source.
  • Quality signal: DORA Report and METR study are empirical counterweights to marketing-adjacent content — always worth surfacing.
  • Noise pattern: Same problem as last gather — “Top N AI Agent Frameworks” listicles still dominate search results. The -"top 7" -"top 10" -"best tools" exclude list helps but doesn’t catch “12 Best…” and similar variants. Consider adding more exclude terms.

2026-03-29 — Initial gather #

Techniques & Methodology #

Tool Landscape #

Agent Frameworks #

Novel Applications #

Key Stats #

  • 84% of developers in latest Stack Overflow survey use or plan to use AI coding tools.
  • Pricing has standardised: $10/mo (Copilot Pro) and $20/mo (Cursor, Windsurf, Claude Code).
  • Wikipedia now has a “Vibe coding” entry — term origin: Andrej Karpathy, Feb 2025.
  • [claude-expertise] The comparison articles inform Claude Code usage choices directly.
  • [vibe-coding-applications] “Vibe Coding Comes to Omics” is a concrete application story.
  • [vibe-coding-applications] “From Vibe Coding to Spec Coding” is about enterprise production readiness.
  • [ai-societal-impact] “Revolution or Risk?” article touches on societal implications of AI coding.

Meta-observations #

  • Keyword suggestion: “spec coding” is emerging as a distinct term — the vibe→spec migration is a real trend.
  • Keyword suggestion: “Kiro” and “Antigravity” are new entrants worth tracking separately.
  • Noise pattern: Tool roundup listicles dominate this space (“10 Best…”, “7 Go-To…”). Need stronger quality filtering — prioritise articles with personal experience, benchmarks, or critical analysis over ranked lists.

Strategy Changelog #

DateChangeReason
2026-03-29Initial strategy createdFirst journal run
2026-03-29Added keywords: methodology/patterns focus, prompt-driven developmentGemini review: technique over tool roundups
2026-04-25Added keywords: Coordinator/Verifier Agent pattern, agentic governanceThree-role agent architecture emerging as formal multi-agent governance standard
2026-04-25Added preferred sources: developers.redhat.com, augmentcode.comRed Hat carries enterprise validation weight; Augment Code produces substantive methodology comparisons