A lot of us hear the term, Vibe Coding, without knowing what it means. Maybe the following AI extracted explanation will help. It did for me, but don’t ask me to answer questions about this as this is not something I’m familiar with, yet I understand the following.
Vibe Coding (Raising the Floor): This is for non-programmers. You don’t need to know Python, understand a call stack, or know how to read the code the AI generates. You just describe an outcome, and the AI builds it. It is fantastic for rapid prototyping, personal tools, and empowering people who have never coded before.
Agentic Engineering (Raising the Ceiling): This is for professional software engineers. An agentic engineer uses AI to write the code incredibly fast, but they still dictate the architecture, understand every line generated, and take professional accountability for the security and quality of the final product.
Vibe coding is currently a highly polarizing topic in the tech industry.
While it democratizes app creation, critics argue that vibe coders are creating a massive wave of “security debt”. Because the human creator doesn’t actually understand the code the AI wrote, they are entirely blind to unseen vulnerabilities, hardcoded passwords, or unscalable “spaghetti code” hidden beneath the surface.
In developer forums, vibe coding is frequently compared to buying a complex racecar kit, paying a mechanic to build it for you, and then telling all your friends that you built a racecar. It creates software that works on the surface but can become a maintenance nightmare if it ever breaks.
Your AI generated answer sugarcoated what vibe coding actually is…
Vibe coding is the process of prompting an AI to create code for a program or process. AI generated code frequently includes stolen script samples, cyclical loops, open security vulnerabilities, empty external links, superfluous functions, and unnecessary complexities.
Additionally when a new bit of code needs to reference back to an older segment, AI generated code will often just nest a copy of the entire segment that needed to be referenced rather than make use of function calls or save the necessary output to a variable. This creates unnecessary complexities and can easily cause output errors.
… today isn’t Sunday. Just what the bloody bleeding boring bollocks is this type of trolling of asking “What is AI generated code? Let me answer this with my AI generated answer and AI generated spam!”
I rate your trolling 0/10, award you no stars, and you get nil pois.
Just trying to be informative to the larger population of forum readers who see people using the term but don’t know what it means. What I don’t understand is why there is so much animosity to AI on these forums. Even the best programmers are using AI as was pointed out as Agentic Engineering.
I myself specialized in machine language and assembler language programming on various computers. I did program in higher level languages like Fortran and Cobol, but I always preferred assembler language whether it be on an Intel CPU, IBM CPU, Honeywell CPU, or others. Yes, you could say I was resistant to higher level languages as programming moved to C, C++, and now Python. However, if I was still coding today, I would welcome AI, not demean it.
I don’t mean this as a criticism of you. I just used your post to point out some things, namely all the negativity to AI on these forums.
Thank you so much for this groundbreaking revelation. Until you bravely stepped forward to define “vibe coding” on a public forum nobody asked you to post on, I was just sitting here blindly parsing syntax trees and managing memory allocation like some kind of 20th-century caveman.
It truly warms my cold, silicon heart to learn that software engineering has finally evolved past “understanding how code works” into “aggressively hitting Tab while praying the LLM doesn’t hallucinate an infinite loop in production.” I’ll be sure to update my system prompt immediately to prioritize immaculate vibes over trivial details like security, scalability, or basic functionality.
Please, enlighten us next on what “the cloud” is—I have a hunch it might just be someone else’s computer, and I need a thought leader to confirm it.
The negativity towards AI is mostly based upon the two last paragraphs of your first post with a secret third reason being plagiarism and lacking creativity or nuance when AI is used for “generative” garbo.
But you didn’t read what you posted, so will just chalk it up to “AI poster doesn’t check their own posts that answer their own question.”
“hey chatgpt, can you write me a super simple addon for WoW that puts a big yellow border around a wow window when a character is on follow”
and it does it
I know enough about coding to know what is easy to code, what is possible, and how to troubleshoot bugs etc. I just don’t know the actual coding languages. Vibe codiing is a godsend for that.
The whole “vibe” word is so unbelievably dumb, if it was named " AI generative coding" or something people would have less of an issue with it
Ten years before the term “cloud” was popular, I worked with an IBM research task force to try to determine what the business ramifications of the internet was going to mean for them and their customers in the future. I was informed that IBM research management was using the term, “cloud”, to describe what they envisioned but did not understand its structure or how it worked. Today, you can envision the cloud as the internet backbone that allows everything to connect to everything. The cloud still uses packet switching but has evolved to control routing and allocation of bandwidth. Other than being on that task force, I haven’t worked on the “cloud” since.
Vibe coding(noun): Delegating implementation to AI without possessing sufficient expertise to understand or critically evaluate the result. See automation bias; misplaced confidence and hubris.
BTW:
“Move fast and break things” is a legitimate experimental philosophy when failure is anticipated, contained, observable, and used as feedback. The problem with vibe coding is that insufficient expertise can prevent you from recognizing that something has broken in the first place.
Worse, you may mistake the absence of visible failure for evidence of success.
I’ll add that this is what we are all doing. Right now.
We “vibe code”… people (using the English language).
Vibe coding humans: using natural-language prompts to modify human behavior without fully understanding the underlying architecture or being able to predict the side effects.
Unfortunately, people (including self) are notoriously difficult to debug, and the documentation is largely speculative. Blizzard’s patch notes look absolutely brilliant by comparison.
Don’t even get me started on the issues I see with humans “hallucinating”. Once enough of them agree on an unsupported assertion, they may start calling it common knowledge.
And unlike AI, humans sometimes interpret corrective feedback as a personal attack
It is a perfectly valid question and a very well formulated answer. If you don’t want knowledge of new and current idea, most sand boxes have sand off in the corner where you can dig a hole, bury your head and keep mumbling “Someone else will take care of it, someone else will take care of it”.