3 ms·

We need a new term for LLMs actually solving a hard problems. When I help Claude Code solve a nasty bug it doesn’t feel like “vibing” as in “I tell the model wh

We need a new term for LLMs actually solving a hard problems. When I help Claude Code solve a nasty bug it doesn’t feel like “vibing” as in “I tell the model what I want the website to look like”. It feels like sniping as in “I spot for Claude Code, telling how to adjust for wind, range, and elevation so it can hit my far away target”.

scosman 11mo ago
From what I recall of the original Karpathy definition, it’s only “vibe coding” if you aren’t reading the code it produces
- lukan 11mo ago
  Yes, I vote for keeping that definition and not throw it all into a box. LLM assisted coding is not vibe coding.
  - kaspermarstal 11mo ago
    My point exactly, it is not vibe coding so it should not be called vibe coding. What should we call it then?
    - embedding-shape 11mo ago
      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.
- kaspermarstal 11mo ago
  Cool, I did not know that. That makes perfect sense.
- JimDabell 11mo ago
  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 https://x.com/karpathy/status/1886192184808149383
fuzzy_biscuit 11mo ago
So we're the spotter in that metaphor. I like it!
- riskable 11mo ago
  "spotter coding" or perhaps "checker coding"? "verified vivisection development" when you're working with older code :D
demarq 11mo ago
- backseat engineer - keyboard princess - Robin to the Batman - meatstack engineer - artificial manager
- kaspermarstal 11mo ago
  Keyboard Princess is good, Artificial Manager is even better.

scosman 11mo ago

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

lukan 11mo ago
Yes, I vote for keeping that definition and not throw it all into a box. LLM assisted coding is not vibe coding.
- kaspermarstal 11mo ago
  My point exactly, it is not vibe coding so it should not be called vibe coding. What should we call it then?
  - embedding-shape 11mo ago
    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.
kaspermarstal 11mo ago
Cool, I did not know that. That makes perfect sense.
JimDabell 11mo ago
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 https://x.com/karpathy/status/1886192184808149383

fuzzy_biscuit 11mo ago

So we're the spotter in that metaphor. I like it!

riskable 11mo ago
"spotter coding" or perhaps "checker coding"? "verified vivisection development" when you're working with older code :D

demarq 11mo ago

- backseat engineer - keyboard princess - Robin to the Batman - meatstack engineer - artificial manager

kaspermarstal 11mo ago
Keyboard Princess is good, Artificial Manager is even better.