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
Maggie Appleton endorses Steve Krouse’s framing that vibe code and legacy code are the same problem: code nobody understands. She treats vibe coding as a spectrum, cites Karpathy’s “forget that the code even exists” definition, and describes keeping Cursor and Claude on a short leash while using them as tutors when understanding slips.
ideas
- Vibe equals legacy when understanding is missing. Code nobody can explain is tech debt whether a human or a model wrote it.
- Vibe coding is a spectrum. Professional developers rarely sit at the all-vibes end; how much you understand measures how hard you are vibing.
- Not all AI-assisted code is vibe code. Accepting output without understanding is the defining move, not merely using a coding model.
- YOLO speed fights learning. She tries to keep handoff minimal and has models walk through code line by line when out of depth.
- Models can teach as well as generate. Targeted exercises help recover understanding after drifting toward high-vibe, low-comprehension work.
quotes
“vibe code and legacy code are roughly the same thing; “code that nobody understands.””
“forget that the code even exists”
“A key part of the definition of vibe coding is that the user accepts code without full understanding.”