The Stanford professor and former Google Brain scientist said the term misleads people into imagining engineers just "go with the vibes" when using AI tools to write code. "It's unfortunate that that's called vibe coding,"
Despite his gripe with the name, Ng is bullish on AI-assisted coding. He said it's "fantastic" that developers can now write software faster with these tools, sometimes while "barely looking at the code."
Which one is it? Is it in-depth assisted coding, or is it fly by the seat of pants and accept anything, style coding? That's why it has a bad name, it's not structured, careful, examined coding, all the time. It's great if you review it, and make sure it's safe, and does what you need, but if you don't? How many projects are being done that aren't being carefully watched and examined, that will have major issues because a developer accepted a block of code, that doesn't exactly do what they needed?
Obviously, the developer can write bad code, which is a different problem, and can be just as serious, if not more serious, but if AI isn't helping that, can worsen it, then why should we overly respect the concept, considering how it can be abused.
Never tell people how to do things. Tell them WHAT to do and they will surprise you with their ingenuity. -- Gen. George S. Patton, Jr.