Talk:Vibe coding

Copyright issues and possible license violations

The article should mention that the possibility that vibe coding may regurgitate pieces of copyrighted code, without the corresponding copyright header and thus violating the code's license. It is discussed in GitHub_Copilot#Licensing_controversy but should equally be discussed here. Professor Tournesol (talk) 06:09, 12 February 2026 (UTC)

A few comments

At the start

Might be worth noting that it creates a lot more than just "security" issues https://en.wikipedia.org/wiki/The_Machine_Stops (quite an exaggerated example and i'm sure there's others but a good read nonetheless)

It's overreliance, lack of understanding, etc and although we could argue that many programmers don't understand exactly how their compilers work, they do understand how their code works, what it does, and eventually what went wrong

Similar cases include when large companies have relied on small GitHub dependencies to get work done and a push has been made to that repository and it has broken their entire code, i suppose this issue could be solved after a rebuild though and is vastly different in some ways

You could ask the AI what went wrong and it could explain it but if it doesn't and you just use the code you would never learn.

The "Impact on open-source software"

section could be generalised / split into another topic ("She also pointed out that language models will not submit useful bug reports to the maintainers, or be aware of potential issues") since this isn't just regarding open-source but programming in general although it is a good example and could possibly be linked to closed source software too

you could talk about

the environmental impact / danger of vibe coding too in regards to electricity usage and "think time", also examples of software made by vibe coding used in large systems like face monitoring could affect people lives incorrectly (i.e if a face scan reports you as a criminal when you're not and if that system could not be challenged in a court or if you are a criminal and you can no longer get food anywhere - again these are really bad examples on my part and aren't real life cases)

although luckily enough afaik no major systems use any products of vibe coding

You could link to the topic of AI on wikipedia and it's criticisms

Some inspiration; https://www.youtube.com/watch?v=cnX5zJ_qGz0 https://www.youtube.com/watch?v=lrZyBciUpLQ ~2026-15286-55 (talk) 10:59, 10 March 2026 (UTC)

Change the title to AI-assisted coding or coding using AI

For the same reason the "gene-centered view of evolution" is not called the "selfish gene theory". Hplotter (talk) 15:48, 14 April 2026 (UTC)

Oppose - This article was written around the term "vibe coding". It no longer makes sense to refer to being word of the year and so on under the new title. Here for the one billionth edit (talk) 16:19, 14 April 2026 (UTC)

I have reverted the move per WP:BOLDMOVE because I believe the common name for the practice described by this page is Vibe coding. Additionally AI-assisted coding and Vibe coding are fundamentally different to the extent that we have AI-assisted software development. If you want to propose to move it anyways, please create a formal WP:Requested Move. Squawk7700 (talk) 16:26, 14 April 2026 (UTC)

I would also oppose moving this page, but it's not clear to me that vibe coding and AI-assisted software development are distinct. I think they are synonymous to most people, and that vibe coding has become the leading term.

I know some people disagree, but I've only come across that stance from people who support the use of LLMs in software development and dislike the connotations of vibe coding. TietoTeekkari (talk) 06:47, 16 April 2026 (UTC)

Oppose - This article was specifically written around the term "vibe coding". Vibe coding is about using AI without any review. The vast majority of programming is now done with AI assistance, so we don't need a special term for merely using AI assistance in some way, for the same reason we don't need a special term for "driving using automatic transmission" which we normally just call "driving". Dwheeler (talk) 17:25, 18 September 2026 (UTC)

Different approach

Specification-driven development with AI This might be good to mention as a different direction and it seems a better one at that. ~2026-38073-05 (talk) 19:47, 3 July 2026 (UTC)