As someone who has been coding for 20 years and now does a lot of vibe coding, you couldn't possibly be more misinformed.
Edit: LOVE the downvotes by the people being left behind in the dust.
I think the problem isn't necessarily with the vibe coding itself, it can produce usable custom applications, but can you produce maintainable code? Is it secure?
Github is having problems with AI slop being submitted for PRs and maintainers being overwhelmed by code that isn't usable, doesn't conform to the project coding standards and the submitter probably has absolutely no idea what the code does, so can't answer questions when asked.
I think one maintainer was claiming that around 10% of the submitted AI code was of a quality high enough to even consider accepting into the project.
Hopefully the quality will improve over time, to a point where AI code submissions are of a high enough quality to be usable and are maintainable.
But vibe coding is more about making a one-shot solution for a small custom application and if it doesn't work, you get the AI to iterate it. That is fine, if it is just for one person or a small group to use, where security holes are not so much of a problem, for example, but producing a codebase that hasn't been tested and using it for the basis of a major project isn't going to work out well at the current time.
Also, a lot of people who can't code are producing apps, again producing something QaD for themselves is fine, it is really freeing, they can get a customised app that does exactly what they want for the fraction of the price of getting it written professionally... But if it goes wrong, they have to drop back on the AI to try and correct it, because they don't understand the code.
If those people are asking AI to write new modules for an existing project and then submitting it, that is not a good situation to be in, especially as the maintainer of the project. Vibe coding has its place and it is a really great thing for really personal software, but it isn't so good for collaboration projects, at least not in its current form.
If the vibe coder can't validate the code produced, they shouldn't be adding it to projects or distributing it as a finished product. What happens when the first user reports a buffer overflow or input sanitation problem? You, as a programmer with 20 years of experience might be able to wade through the code to find the problem, but most people wouldn't have a clue.
I've done some simple vibe coding to get some simple scripts and app done that help me in my day to day job, but I can look at the code and see whether there are any big errors in it, but it has saved me days of extra work, allowing me to concentrate on the tasks at hand - E.g. we are doing an Exchange migration and getting the AI to spit out complex PowerShell scripts to list aliases or add new aliases to the users in the tenant to cover the different domains we use, for example, is very useful and time saving, but I wouldn't use it to create a multi-user system, because it is too complex and there are too many potential security problems it could build into the code.
I think it comes down to the right tool for the job, and vibe coding is still taking baby steps at the moment. It is fascinating and fun, but you need to know its (current) limits and when to use it and I think that is something few of the proponents are talking about, when trying to get people to use it.
