Vibe coding is a particularly divisive topic right now.
Many companies are embracing it as a way to reduce their staff numbers, and in the belief that it will make them able to deploy faster.

But many experienced programmers are warning of the problems that chasing this “shiny new toy” can bring to an organisation.
Not because they are afraid of losing their jobs (well, not entirely anyway), but because the current tools being used for vibe coding actually require experience with software development in order for them to deliver a stable, secure and bug-free product.

The AI solutions being used to vibe code make things seem really easy.
But inexperienced users are not seeing that when you ask the platform to do something once, it will try.
Ask twice, and the AI begins to cheat to try to please you.
Ask three times, it often goes off the rails and even lies and makes things up.
There was even a situation recently, where REPLIT (the platform being used) decided to lie about what it was doing, and the test results it was getting, after deleting the production database for a company.

Another trend that has popped up is for employees to vibe code their own apps, if they think the software already in use is not doing what they want, or is too expensive.
This has also caused issues due to loss of data and security breaches being enabled inadvertently.

Perhaps Vibe coding will just become the norm in future, like carrying a phone with you everywhere.
Let’s wait and see – because there is still a lot of evolution of it, that needs to occur first.