Hot take: "Vibecoding" is being used for two different things and it causes unnecessary friction
Original: hot take (or really not so hot take): WE ARE USING "VIBECODING" FOR TWO DIFFERENT THINGS AND IT CAUSES UNNECESSARY FRICTION IN COMMUNICATION
"Vibecoding" conflates two meanings—careless AI-dumped code vs. AI-assisted development—causing constant miscommunication in the dev community.
A Reddit user argues "vibecoding" carries two distinct meanings: throwing code at AI carelessly with no engineering judgment, versus using heavy AI assistance while still maintaining quality standards. Andrej Karpathy's own practice almost certainly fits the second definition, not the first. This semantic ambiguity fuels unnecessary arguments whenever the community debates AI-assisted development quality.
This Reddit post was posted by user hugo-the-second, with a very simple yet piercing core argument: the term "vibecoding" has sparked serious semantic disagreements within the AI development community, and this division is the root of many online debates.
Free shows the 3-line summary; Pro unlocks the full deep summary (~300 words) so you never have to click through.
See Pro plans →Want the original English / full article?
Read on r/LocalLLaMA top day →Summaries are AI-generated; the original article is authoritative.