I disagree regarding the point about not needing to know how to support the programs created while vibe coding, particularly from an enterprise prospective. If you are producing code that is going to be deployed to a production environment for users to use, it will require support at some point in its lifetime. The argument for AI agents seems to be “Let them do the debugging and code fixes”, but at the same time there are still vicious loops in vibe coding where the AI doesn’t get it right repeatedly or you run out of tokens. Having some human support of enterprise software is critical.
Exactly. The same for code being given away under open source, it needs to be secure and you need someone who is responsible for keeping it safe and organising the project.
Vibe coding is fine for personal use or small groups of users on an internal network. As soon as you get to enterprise software or software deployed on the Internet, you need proper maintenance and support in place.
My friend, who was in my high school computer science class, but has done no computer programming in his career since, is now vibe coding a finance app he hopes to put on the Apple store. I just got a private invite to check it out recently. And all I could think as I was poking around was, how are you actually testing this to make sure the numbers it’s presenting make actual valid sense. Making and selling a finance app that has any math bugs feels like a fast track to landing in court, to me.
This is why financial regulations are so strict and the certification that the software has to attain, before it can be sold/used are so high. For “home” software, it is a different matter, but business financial software generally has to be certified, if it isn’t, a company won’t touch it, because their auditors will auto-fail compliance with financial regulatory reporting, because the software doesn’t have the certification.
User testing, like you are doing, is just the first, small stage of getting financial software approved, at least here in Europe.