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

Gather — 10 April 2026

COBOL / Legacy Modernisation Case Studies #

Citizen Developer Programmes (Enterprise Data) #

Enterprise Vibe Coding Governance #

Comprehension Debt (Deeper Research) #

Enterprise Agentic AI Landscape #

  • Vibe Coding Approaches “Waterfall in Markdown” critique of SDD is relevant to enterprise adoption — if SDD is the governance answer but is methodologically flawed, enterprises are betting on a leaky abstraction.
  • AI Impact on Society T-Mobile / Forrester 506% ROI is the positive counter-narrative to layoff stories; citizen-dev programmes are the “reshape not replace” mechanism made concrete.
  • Data, IP & Training Rights “Copyright void” for AI-generated code (no protection + potential infringement) is the legal backdrop for all enterprise vibe-coding governance — governance must address IP provenance.
  • Claude-Specific Expertise Claude Code’s security incidents (permission bypass) are a direct enterprise-governance concern for the “vibe coding in enterprise” adoption wave.
  • Open vs Closed AI Ecosystems Microsoft Agent Framework’s enterprise-production positioning is targeting the same adoption wave — closed-source framework vs. LangGraph/CrewAI open alternatives.

Meta-observations #

  • Emerging theme: Concrete case studies with numbers are finally appearing (RBC watsonx, T-Mobile Power Platform, Forrester 506% ROI, DOGE academic study). The “we need case studies” gap from last gather is closing — expect Q2 2026 to be rich in enterprise data.
  • Emerging theme: “Cognitive debt” is succeeding “comprehension debt” as the academic term. The ICSE TechDebt 2026 conference session confirms peer-review uptake. Worth tracking which label wins.
  • Emerging pattern: Two distinct enterprise AI-coding governance models are crystallising — (a) Citizen Developer CoE model (top-down, Forrester TEI-style ROI), (b) Vibe Coding Governance model (bottom-up, managing existing dev adoption). Different risk profiles, different metrics.
  • Emerging pattern: The “reshape not replace” thesis (from BCG at societal level) has a concrete developer-level mechanism — citizen devs + professional devs collaborating, with AI enabling both. T-Mobile case study is the canonical example.
  • Keyword suggestion: “citizen developer CoE” (Center of Excellence) — the organisational unit making citizen-dev programmes work.
  • Keyword suggestion: “cognitive debt” — academic-peer-reviewed successor to “comprehension debt.”
  • Keyword suggestion: “vendor lock-in agentic AI” — under-covered risk dimension; Kai Waehner is the best source so far.
  • Source to watch: DigitalDefynd — publishing multiple enterprise Copilot case studies with concrete numbers; useful aggregator.
  • Source to watch: Kai Waehner blog — enterprise-architect perspective on agentic AI adoption. Low volume, high signal.
  • Source to watch: ICSE TechDebt conference proceedings — academic legitimacy for cognitive-debt research.
  • Quality signal: The DOGE case study is the first peer-reviewed academic analysis of a US federal AI-legacy program. Government adoption studies are historically underrepresented; this suggests more to come.
  • Gap: Still no deep case studies from financial services or healthcare — two sectors with large legacy footprints. Goldman Sachs and one global insurer are the only finance cases; no healthcare cases yet.
  • Gap: No European case studies in this cycle. Enterprise adoption data is US-centric; Europe (where AI Act compliance is binding) is invisible.
  • Noise pattern: “Top 10 AI tools for legacy modernization” listicles still dominant; exclude_terms filter working but not perfect.