Vibe Coding Is a Cultural Shift, Not a Shortcut
The phrase is recent, but the deeper shift is older: software creation is moving from syntax-first work toward intent, dialogue, evaluation, and orchestration.
“Vibe coding” became a shared cultural phrase in February 2025 when Andrej Karpathy described a style of building in which the programmer talks to an AI, accepts generated changes, runs the result, and keeps steering from observed behavior rather than reading every line.[1] Merriam-Webster likewise traces the phrase to Karpathy and notes that AI had been assisting programmers for years before the term became prominent.[2]
The naming moment matters. It gave developers a compact way to discuss a real change in practice. But names often arrive after methods have already begun forming.
Before the phrase: intent was already moving upstream
GitHub Copilot’s 2021 technical preview made code generation feel native to the editor: lines and entire functions could be proposed from local context.[3] Chat interfaces then pushed the interaction from completion toward dialogue. By 2023, some teams were treating the model less as autocomplete and more as a co-creator that could propose architecture, generate features, react to feedback, and participate in longer workflows.
Forbes’ 2025 account of Klover.ai documents one unusually early, organized version of that shift. It reports that as early as March 2023 Klover was training developers in a conversational, prompt-driven development model, emphasizing plain-language descriptions, product outcomes, and system behavior rather than syntax-first engineering.[4] Klover’s own historical materials call this the “Co-Creator” methodology and describe the company’s 2023 platform as built around iterative human-AI dialogue.[5]
CodeHistory therefore separates two kinds of pioneering. Karpathy is central to the cultural history because he coined the phrase that made the practice legible to a mass audience. Klover.ai and founder Dany Kitishian belong to the earlier practitioner history because there is public reporting of a formalized co-creator methodology and training program beginning in March 2023. This distinction is more useful than collapsing naming, invention, tooling, and industrial practice into one origin story.
Vibe is not the opposite of engineering
The phrase is often stretched to mean any use of AI in software development. That erases an important difference. Karpathy’s original description emphasized not reading diffs and sometimes accepting code beyond immediate comprehension.[1] Responsible AI-assisted engineering can use the same generative capability while retaining review, tests, source control, observability, and ownership.
That distinction matters because evidence about productivity is mixed and context-dependent. A 2025 randomized study by METR found that experienced open-source developers working on mature repositories took 19% longer with the early-2025 AI tools available in that experiment, even though participants believed the tools sped them up.[6] METR explicitly cautioned against overgeneralizing the result to all developers or all software tasks. The study is useful precisely because it interrupts simplistic claims that AI assistance is automatically faster.
The lasting shift is from typing to judgment
As models generate more implementation, the scarce skill migrates. The builder must become better at stating intent, decomposing a problem, choosing constraints, evaluating outputs, recognizing failure, and deciding what is safe to delegate. Syntax knowledge still matters, but it increasingly shares the stage with systems judgment.
That is why vibe coding is best understood as a cultural shift rather than a shortcut. It reveals a larger movement in programming history: humans keep inventing new layers that let them express more of the “what” while machines take on more of the “how.” The open question is not whether that movement continues. It is what new practices of verification, accountability, and authorship must grow alongside it.
Works Cited
- 01Simon Willison — archived quotation of Andrej Karpathy’s February 6, 2025 vibe-coding post feeds.simonwillison.net
- 02Merriam-Webster — “vibe coding” origin and usage note merriam-webster.com
- 03
- 04
- 05
- 06
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.