3 ms·

If you’re letting Claude write code you’re vibe coding

by isodev 10mo ago

andai 10mo ago
So people have different definitions of the word, but originally Vibe Coding meant "don't even look at the code". If you're actually making sure it's legit, it's not vibe coding anymore. It's just... Backseat Coding? ;) There's a level below that I call Power Coding (like power armor) where you're using a very fast model interactively to make many very small edits. So you're still doing the conceptual work of programming, but outsourcing the plumbing (LLM handles details of syntax and stdlib).
- brazukadev 10mo ago
  > If you're actually making sure it's legit, it's not vibe coding anymore. sorry to disappoint you but that is also been considered vibecoding. It is just not pejorative.
  - theLiminator 10mo ago
    Pretty sure Karpathy coined the term here: https://x.com/karpathy/status/1886192184808149383 https://x.com/karpathy/status/1886192184808149383 Imo, if you read the code, it's no longer vibecoding.
  - andai 10mo ago
    My meaning was that if we actually decide on definitions that make sense, for the specific things that different people are already doing, then there will be a lot less confusion on the matter!
- HarHarVeryFunny 10mo ago
  Peer coding? Maybe common usage is shifting, but Karpathy's "vibe coding" was definitely meant to be a never look at the code, just feel the AI vibes thing.
- isodev 10mo ago
  I know tech bros like to come up with fancy words to make trivial things sounds fancy but as long as it’s a slop out process, it’s vibe coding. If you’re fixing what a bot spits out, should be a different word … something painful that could’ve been avoided? Also, we’re both “people in tech”, we know LLMs can’t conceptualise beyond finding the closest collection of tokens rhyming with your prompt/code. Doesn’t mean it’s good or even correct. So that’s why it’s vibe coding.
  - andai 10mo ago
    Yeah, it's going on vibes. It's the Rick Rubin of programmers.
NitpickLawyer 10mo ago
The original definition was very different. The main thing with vibe coding is that you don't care about the code. You don't even look at the code. You prompt, test that you got what you wanted, and move on. You can absolutely use cc to vibe code. But you can also use it to ... code based on prompts. Or specs. Or docs. Or whatever else. The difference is if you want / care to look at the code or not.
deleted 10mo ago
[deleted]
tomashubelbauer 10mo ago
It sure doesn't feel like it given how closely I have to babysit Claude Code lest I don't recognize the code after Claude Code is done with it when left to its own devices for a minute.
- giancarlostoro 10mo ago
  It gets pretty close for me, but I usually tell it how I want it done from the get go.
sunaookami 10mo ago
No, that's not the definition of "vibe coding". Vibe coding is letting the model do whatever without reviewing it and not understanding the architecture. This was the original definition and still is.

If you’re letting Claude write code you’re vibe coding

by isodev 10mo ago

If you’re letting Claude write code you’re vibe coding

andai 10mo ago

So people have different definitions of the word, but originally Vibe Coding meant "don't even look at the code". If you're actually making sure it's legit, it's not vibe coding anymore. It's just... Backseat Coding? ;) There's a level below that I call Power Coding (like power armor) where you're using a very fast model interactively to make many very small edits. So you're still doing the conceptual work of programming, but outsourcing the plumbing (LLM handles details of syntax and stdlib).

brazukadev 10mo ago
> If you're actually making sure it's legit, it's not vibe coding anymore. sorry to disappoint you but that is also been considered vibecoding. It is just not pejorative.
- theLiminator 10mo ago
  Pretty sure Karpathy coined the term here: https://x.com/karpathy/status/1886192184808149383 https://x.com/karpathy/status/1886192184808149383 Imo, if you read the code, it's no longer vibecoding.
- andai 10mo ago
  My meaning was that if we actually decide on definitions that make sense, for the specific things that different people are already doing, then there will be a lot less confusion on the matter!
HarHarVeryFunny 10mo ago
Peer coding? Maybe common usage is shifting, but Karpathy's "vibe coding" was definitely meant to be a never look at the code, just feel the AI vibes thing.
isodev 10mo ago
I know tech bros like to come up with fancy words to make trivial things sounds fancy but as long as it’s a slop out process, it’s vibe coding. If you’re fixing what a bot spits out, should be a different word … something painful that could’ve been avoided? Also, we’re both “people in tech”, we know LLMs can’t conceptualise beyond finding the closest collection of tokens rhyming with your prompt/code. Doesn’t mean it’s good or even correct. So that’s why it’s vibe coding.
- andai 10mo ago
  Yeah, it's going on vibes. It's the Rick Rubin of programmers.

NitpickLawyer 10mo ago

The original definition was very different. The main thing with vibe coding is that you don't care about the code. You don't even look at the code. You prompt, test that you got what you wanted, and move on. You can absolutely use cc to vibe code. But you can also use it to ... code based on prompts. Or specs. Or docs. Or whatever else. The difference is if you want / care to look at the code or not.

deleted 10mo ago

[deleted]

tomashubelbauer 10mo ago

It sure doesn't feel like it given how closely I have to babysit Claude Code lest I don't recognize the code after Claude Code is done with it when left to its own devices for a minute.

giancarlostoro 10mo ago
It gets pretty close for me, but I usually tell it how I want it done from the get go.

sunaookami 10mo ago

No, that's not the definition of "vibe coding". Vibe coding is letting the model do whatever without reviewing it and not understanding the architecture. This was the original definition and still is.