saved
Vibe code is legacy code
Hraness wrote this summary from a saved copy of the source. Quotations are taken word for word from the source.
gist
Steve Krouse defines vibe coding as Karpathy’s practice of forgetting the code exists, and equates that with legacy code: tech debt you cannot debug or extend. He places vibe coding on an understanding spectrum, warns non-programmers against large maintained projects, and argues serious AI-assisted work still needs theory building and a tight leash on the model.
ideas
- Vibe coding means forgetting the code exists. Karpathy’s coinage is acceptance without understanding, not every use of an AI coding tool.
- Ununderstood code is legacy debt. Time to debug and change unfamiliar code is the cost; programming is theory building, not line count.
- Throwaways are the fit. Prototypes you will not maintain can be vibed; maintenance turns the same output into debt.
- Understanding is a spectrum. Asking for a web app with a database already vibes less than asking for an unspecified “app.”
- Credit-card debt is the metaphor for non-programmers. Fixing broken vibe code only with more AI is like paying a card with another card.
quotes
“forget that the code even exists.”
“We already have a phrase for code that nobody understands: legacy code.”
“When you vibe code, you are incurring tech debt as fast as the LLM can spit it out.”
“Programming is fundamentally theory building, not producing lines of code.”