5 ms·

Hi Simon, thanks for your comment. I’m the author, just discovering the thread here on HN (and thanks everyone for the enthusiasm!). I do think we need a new d

Hi Simon, thanks for your comment. I’m the author, just discovering the thread here on HN (and thanks everyone for the enthusiasm!). I do think we need a new definition for vibe-coding, because the way the term is used today shouldn’t necessarily include “not even reading the code”. I’m aware that Karpathy’s original post included that idea, but I think we now have two options: - Let the term vibe-coding evolve to cover both those who read the code and those who don’t. - Or define a new term — something that also reflects production-grade coding where you actually read the code. If that’s not vibe-coding, then what is it? (To me, it still feels different from traditional coding.)

simonw 1y ago
I've been calling it AI-assisted development, but that's clearly not snappy enough. I have a few problems with evolving "vibe coding" to mean "any use of LLMs to help write code: 1. Increasingly, that's just coding. In a year or so I'll be surprised if there are still a large portion of developers who don't have any LLM involvement in their work - that would be like developers today who refuse to use Google or find useful snippets on Stack Overflow. 2. "Vibe coding" already carries somewhat negative connotations. I don't want those negative vibes to be associated with perfectly responsible uses of LLMs to help write code. 3. We really need a term that means "using prompting to write unreviewed code" or "people who don't know how to code who are using LLMs to produce code". We have those terms today - "vibe coding" and "vibe coders"! It's useful to be able to say "I just vibe-coded this prototype" and mean "I got it working but didn't look at the code" - or "they vibe-coded it" as a warning that a product might not be reviewed and secure.
- ckcheng 1y ago
  I propose: Software Development/Engineering with “Gen AI Assistance” (yes, “Gaia” [1]. Also spelled “Gaea” in engineering communities). Just like no one speaks of vibe-aeronautics-engineering when they’re “just” using CAD. More specifically, GAIA in SDE produces code systematically with human in the loop to systematically ensure correctness. e.g. Like the systematic way tptacek has been describing recently [2]. [1] https://en.m.wikipedia.org/wiki/Gaia https://en.m.wikipedia.org/wiki/Gaia [2] https://news.ycombinator.com/item?id=44163063 https://news.ycombinator.com/item?id=44163063 Briefly summarized here I guess: https://news.ycombinator.com/item?id=44296550 https://news.ycombinator.com/item?id=44296550
  - 8n4vidtmkvmk 1y ago
    I don't think Googlers will be very fond of that acronym.
    - ckcheng 1y ago
      Why? I doubt they’d confuse Gen AI Assistance with an ID management system?
      - 8n4vidtmkvmk 1y ago
        Still doesn't help to overload the term and ruin search results.
visarga 1y ago
> If that’s not vibe-coding, then what is it? Blind-coding.
a_spy 1y ago
[dead]

simonw 1y ago

I've been calling it AI-assisted development, but that's clearly not snappy enough. I have a few problems with evolving "vibe coding" to mean "any use of LLMs to help write code: 1. Increasingly, that's just coding. In a year or so I'll be surprised if there are still a large portion of developers who don't have any LLM involvement in their work - that would be like developers today who refuse to use Google or find useful snippets on Stack Overflow. 2. "Vibe coding" already carries somewhat negative connotations. I don't want those negative vibes to be associated with perfectly responsible uses of LLMs to help write code. 3. We really need a term that means "using prompting to write unreviewed code" or "people who don't know how to code who are using LLMs to produce code". We have those terms today - "vibe coding" and "vibe coders"! It's useful to be able to say "I just vibe-coded this prototype" and mean "I got it working but didn't look at the code" - or "they vibe-coded it" as a warning that a product might not be reviewed and secure.

ckcheng 1y ago
I propose: Software Development/Engineering with “Gen AI Assistance” (yes, “Gaia” [1]. Also spelled “Gaea” in engineering communities). Just like no one speaks of vibe-aeronautics-engineering when they’re “just” using CAD. More specifically, GAIA in SDE produces code systematically with human in the loop to systematically ensure correctness. e.g. Like the systematic way tptacek has been describing recently [2]. [1] https://en.m.wikipedia.org/wiki/Gaia https://en.m.wikipedia.org/wiki/Gaia [2] https://news.ycombinator.com/item?id=44163063 https://news.ycombinator.com/item?id=44163063 Briefly summarized here I guess: https://news.ycombinator.com/item?id=44296550 https://news.ycombinator.com/item?id=44296550
- 8n4vidtmkvmk 1y ago
  I don't think Googlers will be very fond of that acronym.
  - ckcheng 1y ago
    Why? I doubt they’d confuse Gen AI Assistance with an ID management system?
    - 8n4vidtmkvmk 1y ago
      Still doesn't help to overload the term and ruin search results.

visarga 1y ago

> If that’s not vibe-coding, then what is it? Blind-coding.

a_spy 1y ago

[dead]