{"slug": "is-vibe-coding-dead-or-just-renamed-what-the-record-shows", "title": "Is vibe coding dead, or just renamed? What the record shows", "summary": "Vibe coding is not dead but is being renamed as its original meaning splits into two distinct modes, according to an analysis of industry data and statements from its inventor Andrej Karpathy and Google. Karpathy, who coined the term in February 2025, told Sequoia's AI Ascent audience in April 2026 that the future belongs to 'agentic engineering' for professionals, while Google published a 51-page whitepaper in May 2026 with 'vibe coding' in the title and taught it to over a million people. The practice is at all-time highs: 90% of software professionals use AI at work per Google's DORA survey, and 51% of professional developers use it daily per Stack Overflow's 2025 survey.", "body_md": "The Study · Explainer\n\n# Is vibe coding dead, or just renamed? What the record shows\n\nNo. Vibe coding is not dead, and the confusion is worth clearing up precisely, because the people supposedly burying it are its own inventor and its biggest institutional backer. In April 2026 Andrej Karpathy, who [coined the term](https://x.com/karpathy/status/1886192184808149383) in February 2025, told Sequoia’s AI Ascent audience the future belongs to something he now calls [agentic engineering](https://karpathy.bearblog.dev/sequoia-ascent-2026/). Trade press ran the funeral: [vibe coding is passé](https://thenewstack.io/vibe-coding-is-passe/). A month later Google published [a 51-page whitepaper](/study/new-sdlc-with-vibe-coding/) with vibe coding in the title and taught it to a course audience of over a million. Words do not get eulogized and institutionalized in the same quarter when they are dying. They do it when they are splitting. That is what the record shows, and this piece walks through it with the receipts, including a search-interest handoff we measured ourselves.\n\n## The short version\n\n**The practice is at all-time highs.**[90% of software professionals](https://dora.dev/dora-report-2025/)use AI at work per Google’s own DORA survey, 51% of professional developers[use it daily](https://survey.stackoverflow.co/2025), and the flagship vibe-coding tools post the[best loyalty scores in the category](https://blog.jetbrains.com/research/2026/04/which-ai-coding-tools-do-developers-actually-use-at-work/). Nothing about that curve says dead.**The word is being demoted, on purpose.** It stretched from Karpathy’s original meaning, building without reading the code, into a name for all AI-assisted development. The correction now underway shrinks it back to the casual end, and gives the disciplined end its own title: agentic engineering.**The handoff is measurable.** In our own Google Trends pull, the two terms went from a 30-to-1 search gap in July 2025 to roughly 2.5-to-1 at the June 2026 peak. “Vibe coding” search interest has fallen by about half from its March 2026 high.**For a working builder this is positioning, and it pays.** The word you use tells a client exactly how much verification they are buying. The last section is the translation guide.\n\n## Who declared it dead, exactly\n\nTrace the obituary to its sources and something interesting happens: none of them claim people stopped building this way. The New Stack’s headline says Karpathy has [a new name for the future](https://thenewstack.io/vibe-coding-is-passe/), which is a claim about vocabulary. Karpathy’s own talk drew a line between two modes: vibe coding [raises the floor](https://karpathy.bearblog.dev/sequoia-ascent-2026/), letting anyone build software, while agentic engineering raises the ceiling of what professionals can ship, coordinating fallible agents while preserving correctness, security, and taste. And Google’s whitepaper, the closest thing the field has to an official position, spends fifty pages arguing the two are [ends of one spectrum](/study/new-sdlc-with-vibe-coding/), with the dividing line drawn at verification rather than tools.\n\nSo the death notice, read carefully, says: the word stopped meaning one thing. That is true, and it was true before anyone called it passé. The dictionary saw it coming.\n\n## The timeline of the name\n\nThe sequence tells the story better than any hot take. Karpathy [named the mode](https://x.com/karpathy/status/1886192184808149383) in February 2025: give in to the vibes, forget the code exists, paste the errors back in. Within a month the term was stretching, and Simon Willison published the correction that still holds up: if you review and understand every generated line, [you are not vibe coding](https://simonwillison.net/2025/Mar/19/vibe-coding/). By October 2025 Willison was proposing [vibe engineering](https://simonwillison.net/2025/Oct/7/vibe-engineering/) as a deliberately self-contradictory name for the disciplined version. In November, [Collins Dictionary crowned vibe coding Word of the Year](https://www.collinsdictionary.com/woty), the surest sign a technical term has escaped its technical meaning. By April 2026 the coiner himself [introduced agentic engineering](https://karpathy.bearblog.dev/sequoia-ascent-2026/) for the professional end, and by May, Google’s whitepaper and its [1.5-million-learner course](https://blog.google/innovation-and-ai/technology/developers-tools/kaggle-genai-intensive-course-vibe-coding-june-2026/) had turned the split into curriculum.\n\nNote the irony in the middle of that list. The dictionary crowning and the naming correction happened in the same season. Words get Word of the Year when everyone uses them; words get replaced when everyone uses them for too many different things. Both happened to vibe coding, in order, for the same reason.\n\n## The handoff, measured\n\nWe pulled the two terms head to head from Google Trends ourselves, US web search, twelve months, on one shared scale. Nobody covering the “passé” story showed this chart, which is a shame, because it is more honest than either the funeral or the denial.\n\nThree things are true at once in that data. First, “vibe coding” search interest peaked in early March 2026 and has fallen by roughly half since, from an indexed 100 down to the mid-40s by mid-July. Second, “agentic engineering” went from a rounding error, indexed at 2 in July 2025, to the mid-20s during Google’s course week in June 2026, closing a 30-to-1 gap to roughly 2.5-to-1 at its peak. Third, the handoff is incomplete and may stay that way: in the July lull the older term still leads by about seven to one, and it remains the phrase with the [dictionary title](https://www.collinsdictionary.com/woty), the Google whitepaper title, and the course branding. The searchers arriving behind it are asking new long-tail questions too; the fastest risers on the challenger term are “agentic engineering patterns” and “harness engineering,” which is exactly what you would expect people to ask [once the harness becomes the product](/study/new-sdlc-with-vibe-coding/).\n\nThe flags, since we keep them on for our own charts as well: this is one country, one search engine, web search only, and Trends indexes relative interest rather than absolute volume. It measures what people call the thing, which is precisely the question here, and nothing more.\n\n## The practice never dipped\n\nIf the practice were dying you would see it in adoption, spend, or satisfaction, and every one of those lines points the other way. Google’s own DORA research puts AI use among software professionals [at 90%](https://dora.dev/dora-report-2025/), up 14 points year over year. Stack Overflow’s 49,009-developer survey has [51% of professionals using AI daily](https://survey.stackoverflow.co/2025). JetBrains’ April 2026 survey of 10,000-plus developers found the core vibe-coding tools holding [the highest satisfaction in the category](https://blog.jetbrains.com/research/2026/04/which-ai-coding-tools-do-developers-actually-use-at-work/). The money receipts run through the same period: the [$80 million Base44 exit](https://www.wix.com/press-room/home/post/wix-further-expands-into-vibe-coding-with-acquisition-of-base44-a-hyper-growth-startup-that-simplif), the billion-dollar tool revenue ramps, the whole case [we assembled with the flags on](/study/is-vibe-coding-worth-it/). A practice does not post record adoption, record loyalty, and eight-figure exits while dying. Only its name can die, and even the name is merely getting a narrower job description.\n\nWhether the narrowed practice is fast, safe, and worth the maintenance bill is a different question with its own evidence, and we keep those pieces current: [the speed data](/study/does-ai-coding-make-you-faster/), [the agent reliability data](/study/do-ai-agents-work-yet/), and [the economics verdict](/study/is-vibe-coding-worth-it/).\n\n## What to say instead, and when\n\nHere is the practical payoff, because for a solo builder this vocabulary shift is a positioning gift. The whitepaper makes the point with a scenario: telling a CTO you vibe coded their payment system should raise alarms, while describing the same AI leverage operating under human-designed constraints and test coverage is a different conversation. The words now carry the verification promise.\n\nSo use them precisely, in both directions. “Vibe coding” is still the right term, and now a usefully scoped one, for what it originally meant: the weekend prototype, the exploration, the disposable script where speed-to-signal is the whole point and [the stack costs almost nothing](/primer/vibe-coding-stack/). Claim it without embarrassment; it is the mode that raises the floor. The moment you are selling work that strangers will depend on, describe the discipline instead: AI-assisted implementation with the code reviewed, tests written first, and [an agent setup you actually maintain](/primer/how-to-use-claude-code/). If you want the one-word version the field is converging on, it is agentic engineering. Clients are beginning to search the difference; being the builder who can explain it is cheap authority.\n\n## The verdict\n\nNot dead. Renamed at the top, narrowed at the bottom, and bigger than ever in the middle. The pattern is older than software: a word gets coined for a fringe behavior, the behavior wins, and the word splits into a casual sense and a professional sense with its own title. Vibe coding went from [a February 2025 post](https://x.com/karpathy/status/1886192184808149383) to [Word of the Year](https://www.collinsdictionary.com/woty) to a [Google-taught spectrum](/study/new-sdlc-with-vibe-coding/) in sixteen months, which is the trajectory of a winner, and the search data shows the professional half of the vocabulary rising without the practice missing a beat. Karpathy’s own framing settles the question cleanly: the casual mode keeps “raising the floor for everyone,” and the disciplined mode now has a name for raising the ceiling. Learn the discipline, keep both words, and use whichever one honestly describes the verification behind the thing you shipped.\n\nOne email, when there's something worth sending\n\n## Get the research in your inbox.\n\nNo fixed schedule, no filler. You get an email when we've tested something, run the numbers, or found a tool worth your time.\n\nFree. Double opt-in, unsubscribe in one click.\n\nWhat do you call what you do? [Compare notes in the forum ↗](https://community.okaneland.com)\n\n## Sources & how we researched this\n\n- Andrej Karpathy (Feb 2, 2025), the post that coined vibe coding. x.com/karpathy/status/1886192184808149383\n- Andrej Karpathy (April 30, 2026), Sequoia AI Ascent talk and his own summary post introducing 'agentic engineering': vibe coding raises the floor, agentic engineering raises the ceiling. karpathy.bearblog.dev/sequoia-ascent-2026\n- The New Stack (2026), 'Vibe coding is passé. Karpathy has a new name for the future of software.' thenewstack.io/vibe-coding-is-passe\n- Collins Dictionary (Nov 6, 2025), 'vibe coding' named Word of the Year 2025. collinsdictionary.com/woty; CNN coverage, cnn.com\n- Simon Willison (March 2025), 'Not all AI-assisted programming is vibe coding.' simonwillison.net\n- Simon Willison (Oct 7, 2025), 'Vibe engineering,' his proposed name for the disciplined end. simonwillison.net/2025/Oct/7/vibe-engineering\n- Google (May 2026), 'The New SDLC With Vibe Coding' whitepaper (Osmani, Saboo, Kartakis), which formalizes the vibe coding to agentic engineering spectrum. kaggle.com/whitepaper-the-new-SDLC-with-vibe-coding\n- Google blog (June 2026), 5-Day AI Agents intensive vibe coding course announcement; the Nov 2025 run reached 1.5M+ learners. blog.google\n- Google Trends (pulled July 24, 2026), 'vibe coding' vs 'agentic engineering,' US web search, 12 months, compare mode (one shared 0-100 scale). Chart data in this piece is our own pull.\n- Google Cloud DORA (2025), 'State of AI-assisted Software Development' (~5,000 respondents): 90% of software professionals use AI at work. dora.dev/dora-report-2025\n- Stack Overflow 2025 Developer Survey (49,009 respondents): 51% of professional developers use AI tools daily. survey.stackoverflow.co/2025\n- JetBrains research (April 2026), 'Which AI coding tools do developers actually use at work' (10,000+ developers): category-leading satisfaction for the core vibe-coding tools. blog.jetbrains.com\n- Wix press release (June 2025), acquisition of Base44: ~$80M initial consideration plus earn-outs. wix.com/press-room", "url": "https://wpnews.pro/news/is-vibe-coding-dead-or-just-renamed-what-the-record-shows", "canonical_source": "https://okaneland.com/study/is-vibe-coding-dead/", "published_at": "2026-07-27 13:00:00+00:00", "updated_at": "2026-07-27 23:57:44.791831+00:00", "lang": "en", "topics": ["artificial-intelligence", "ai-tools", "ai-agents", "developer-tools"], "entities": ["Andrej Karpathy", "Sequoia", "Google", "The New Stack", "Simon Willison", "DORA", "Stack Overflow", "JetBrains"], "alternates": {"html": "https://wpnews.pro/news/is-vibe-coding-dead-or-just-renamed-what-the-record-shows", "markdown": "https://wpnews.pro/news/is-vibe-coding-dead-or-just-renamed-what-the-record-shows.md", "text": "https://wpnews.pro/news/is-vibe-coding-dead-or-just-renamed-what-the-record-shows.txt", "jsonld": "https://wpnews.pro/news/is-vibe-coding-dead-or-just-renamed-what-the-record-shows.jsonld"}}