"When I get error messages I just copy paste them in with no comment, usually that fixes it. 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. It's not too bad for throwaway weekend projects, but still quite amusing. I'm building a project or webapp, but it's not really coding - I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works."
"Note that Karpathy was using vibe coding for "throwaway weekend projects," not his day job. He also deprecates the way he asks for "the dumbest things," because he's "too lazy to find it." He says vibe coding is possible "because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good." He also says "it mostly works.""
""Mostly works" is not a glowing recommendation, and applying vibe coding to serious projects presents serious risks, including the creation of hidden bugs that will bite you later. It's folly. It also inevitably creates technical debt. If someone competent and experienced cleans"
Vibe coding is a workflow where developers rely on LLMs to generate and modify code while avoiding detailed understanding of the codebase. The process can involve accepting changes without reading diffs, copying error messages into the system, and making repeated requests until issues disappear. This approach can work for throwaway weekend projects, but it carries risks for serious work. “Mostly works” implies incomplete reliability, and the lack of review can introduce hidden bugs. Over time, these issues accumulate as technical debt, making future maintenance harder and more expensive.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]