Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

From what I recall of the original Karpathy definition, it’s only “vibe coding” if you aren’t reading the code it produces




Yes, I vote for keeping that definition and not throw it all into a box. LLM assisted coding is not vibe coding.

My point exactly, it is not vibe coding so it should not be called vibe coding. What should we call it then?

LLM-assisted Development. Something that for me works in practice, vibe-coding never did, you really need to carefully review and steer constantly if things are to work out longer than just a few features.

You’re right. It’s explicitly about not caring about the code:

> 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. It's possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper so I barely even touch the keyboard. 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. 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.

https://x.com/karpathy/status/1886192184808149383


Cool, I did not know that. That makes perfect sense.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: