<- all tokdocs

Vibe Coding's Limits: What Karpathy's Original Post Already Said

By , founder of Mavric and Apso

View on TikTok ->

Vibe coding is building software by prompting an AI model and accepting what it writes without reading the code closely. A TikTok from @azeem6744 frames its difficulty as something "everyone says," after the creator hit a backend bug at 4 a.m. that he could not fix. The person who coined the term described that exact failure in the original post.

What did Karpathy's original vibe coding post say?

Andrej Karpathy coined "vibe coding" in a post on X, status 1886192184808149383. x.com returned HTTP 402 to my fetch, so I decoded the post ID instead. X's snowflake IDs store a millisecond timestamp, and this one decodes to 2025-02-02 23:17:15 UTC. Wikipedia's article on the term cites the same status URL for the coinage.

Simon Willison's post of 2025-03-19 reproduces the text. Three lines in it match the situation in the video:

  • "It's not too bad for throwaway weekend projects, but still quite amusing."
  • "The code grows beyond my usual comprehension, I'd have to really read through it for a while."
  • "Sometimes the LLMs can't fix a bug so I just work around it or ask for random changes until it goes away."

Willison's post dates the coinage "February 6th." The post ID contradicts that by four days, so I am going with the ID.

Karpathy was describing his own experience as a researcher who could read the code if he chose to. The presenter in the video says he cannot. The difficulty the video attributes to "everyone" was part of the definition from the first day.

What happens in the video?

The narration sets up a contrast: "everyone says vibe coding is not so easy and then i was like well i vibe coded my whole ui and everything works so how bad can it be." Then: "today i tried connecting the back end and it's been an absolute shit show."

He has been debugging "for literally hours," it is 4 a.m., and he says "i don't know how to code so it's like what am i going to do to fix this." The video does not claim the problem was solved. It ends with "i know i will figure it out inshallah."

The caption adds "AI is in a much different place now than it was a year ago." It names no model, vendor, benchmark or price, so there is nothing to check it against.

Where is the line between vibe coding and AI-assisted development?

Willison draws the line this way: "If an LLM wrote the code for you, and you then reviewed it, tested it thoroughly and made sure you could explain how it works to someone else that's not vibe coding, it's software development." His own rule is that he will not commit code "if I couldn't explain exactly what it does to somebody else."

By that test, "i vibe coded my whole ui and everything works" combined with "i don't know how to code" puts the UI on the vibe-coding side. A UI can be judged by looking at it. A backend connection fails with an error message that someone has to read and understand. The video records the point where looking at the output stopped being enough.

How widespread is the term "vibe coding"?

The term spread fast. Collins Dictionary named "vibe coding" its Word of the Year 2025 in a post dated 2025-11-06. It defined the term as "the use of artificial intelligence prompted by natural language to write computer code" and credited Karpathy. The shortlist it beat included "clanker," "broligarchy," "taskmasking," "aura farming," "biohacking," "HENRY," "micro-retirement," "coolcation" and "glaze."

Wikipedia's article states that Merriam-Webster listed the term as "slang & trending" in March 2025. The Merriam-Webster page returned HTTP 403 to my fetch, so that date rests on Wikipedia.

The term was 20 months old when this video was uploaded.

About the video itself

Every frame carries the title "The truth about vibecoding" and the note "Filmed Sept 25," with no year. The upload date is 2026-10-14, so if the filming year is 2026 the clip sat for 19 days before posting. The last frames label it "FOLLOW ALONG · DAY 5," which presents it as part of a series.

The creator says the channel is growing. I could not confirm that, because the follower count was not available and the profile page did not load for my fetch.

Bottom line

The video accurately records what vibe coding feels like when it breaks. The failure it describes, an AI that cannot fix a bug for someone who cannot read the code, is the same one Karpathy wrote into his February 2025 post. By Simon Willison's test, the gap between a working UI and a broken backend is the gap between vibe coding and software development.

Sources

Published October 14, 2026. Based on a TikTok by @azeem6744. Full video notes (markdown)