Historical source material recovered on 2026-09-09. Capture dates and source limitations apply; recovery is not fresh verification.

Vibe Coding

Vibe coding is an informal AI-assisted development style where a person describes what they want in natural language, accepts or iterates on the generated code, and relies mostly on quick manual checks instead of structured specification, tests, evals, and architecture review [src-055, src-094].

Key points

  • Karpathy popularised the term for a looser style of AI-assisted programming, where the developer follows the model's output and fixes issues by feeding errors back into the prompt [src-055, src-094].
  • [src-094] treats vibe coding and Agentic Engineering as endpoints on a spectrum, not mutually exclusive tool categories.
  • The production risk is weak verification: if the only question is whether the output "seems to work", the workflow remains vibe coding even if it uses advanced models or long prompts [src-094].
  • Vibe coding can be useful for exploration, learning, prototypes, or low-stakes experiments, but it creates maintenance, security, and token-cost debt when used for serious systems without a harness [src-094].
  • The practical upgrade path is to add structure: explicit specs, architectural context, tests, evals, guardrails, observability, and human judgement [src-094].
  • A BMAD creator demonstration makes that upgrade path concrete: the loose prompt is converted into durable brainstorming, requirements, architecture and story artefacts before implementation. This shows a structured practice, while the creator's claims about code quality, hallucination avoidance and cost remain unverified outcomes [src-522].

Related entities

Related concepts

Source references

Historical recovered snapshot — 2026-08-03

Preserved from pr-123. Documentary recovery on 2026-09-09; claims below retain their historical source scope and were not freshly verified. Current synthesis above remains authoritative.

  • Numerama/The Conversation describes review saturation and decision fatigue as potential costs of high-volume AI-assisted coding [src-289].

Robin Cartier perspective

This page is part of Robin Cartier's working AI knowledge graph: a practical research layer for production AI, recommendation systems, experimentation, GEO, and agentic web readiness.

The useful next step is to connect this concept back to applied product leadership and operating models.

Recommended next

Keep reading from this thread

From 500 indexed pages and articles.

  1. Wiki concept Software Factory Model The software factory model is the idea that, in mature AI-assisted development, the developer's main output becomes the system that produces code: specifications Related by 094
  2. Wiki concept Agentic Engineering The professional discipline of coordinating powerful, stochastic coding agents to move faster without sacrificing the quality bar expected from serious software Related by vibe
  3. Wiki concept Agentic Software Development Lifecycle Historical source material recovered on 2026-09-09. Capture dates and source limitations apply; recovery is not fresh verification. Readers have engaged with this next