Thread

Karpathy's one-year vibe coding retrospective

Andrej Karpathy · x.com

The person who coined the term reflects on what the year taught everyone.

Open on x.com ↗

The question it answers

  1. When does an AI-built internal tool break down, and when should I bring in a professional developer?

Read with it

  1. The headline stat founders need: most AI-built production apps eventually needed rescue engineering. getcreatr.com Article Vibe Coding Technical Debt: 8,000 Startups Are Now Paying to Rebuild Creatr
  2. An AI engineer explains why generated debt is invisible to the person who shipped it. zenvanriel.com Article Vibe Coding Technical Debt Crisis: What Engineers Must Know Zen van Riel
  3. Names the Spaghetti Point and the three events that expose it. getautonoma.com Article Vibe Coding Technical Debt: The 90-Day Reckoning Autonoma
  4. A rescue shop describes what they find when founders bring in broken AI-built tools. amplifilabs.com Article The Hidden Risks of Vibe Coding and the Technical Debt It Leaves Behind Amplifi Labs
  5. Peer-level research, not vendor content, on how vibe-coded systems degrade. arxiv.org Article Vibe Coding in Practice: Flow, Technical Debt (research paper) arXiv researchers
  6. An honest longitudinal account of where AI-first building holds up and where it collapses. arxiv.org Article Context Before Code: An Experience Report on Vibe Coding in Practice arXiv researchers
eChai Partner Brands The partnership →