The definition given for "vibe coding" is obviously generated, and very much at odds with Karpathy's own description, which includes bits like:
"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."
"...it's not really coding - I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works."
Doesn't sound so much like a seamless fusion.Anyone actually interested in growing as a developer should run screaming from anyone who promises that you can level up by substituting actual expertise for a model that will gladly give you bug-riddled code you don't understand and can't fix on your own.