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
[2] https://news.ycombinator.com/item?id=44163063
Briefly summarized here I guess: https://news.ycombinator.com/item?id=44296550
Re:Read your code
by 8n4vidtmkvmk on Monday August 04, 2025 @06:29PM
(#44792058)
I don't think Googlers will be very fond of that acronym.
Why? I doubt they’d confuse Gen AI Assistance with an ID management system?
Re:Read your code
by 8n4vidtmkvmk on Tuesday August 05, 2025 @10:21AM
(#44798314)
Still doesn't help to overload the term and ruin search results.
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.