3 ms·
This is the origin of vibe coding: https://x.com/karpathy/status/1886192184808149383 https://x.com/karpathy/status/1886192184808149383 > There's a new kind of
by viraptor 1y ago
This is the origin of vibe coding: https://x.com/karpathy/status/1886192184808149383 https://x.com/karpathy/status/1886192184808149383
> There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. (...) I ask for the dumbest things like "decrease the padding on the sidebar by half" because I'm too lazy to find it. I "Accept All" always, I don't read the diffs anymore. (...)
Pair programming still very much deals with code and decisions.
- westurner 1y agoSo, pair programming continues to emphasize software quality (especially with LLMs) but "vibe coding" is more of a "whoo, I'm a reckless magician" (in a less risky application domain) sort of thing? But doesn't a 'vibe-coding' "we'll just sort out the engineering challenges later" ensure that there will be re-work and thus less overall efficiency?