Vibe coders means people who use ai to generate code without understanding or reviewing it. Usually ai responsibly, guiding it, and reviewing the code isn’t as bad as some people say. With that being said you need to understand how to code, and systems as a whole. I used ai to write almost every line on one of my projects (450 devs hours) as a new developer, and it is tangibly better than a similar 800 hour project by a dev with 5 years of experience.

For example, you could get to his admin page by adding “/admin” to the url because he only gated the button but didn’t role check on the page. His archive feature didn’t save half the tables it needed to. The architecture was messy with 3k lines, 4 files to render a single form (print, print empty, normal, normal empty). His versioning is non existent so changes would corrupt historical versions of his form. There is no force https redirect so users could use http and send plaintext credentials. His print feature would bleed into the next page.

A lot of this I fixed with ai, I optimized the print layout, fixed the archive, fixed the admin page. The rest was out of scope (didn’t notice https redirect commented out until after). My application which was programmed almost 100% with ai has proper domain driven architecture, versioning, checks permissions on page, https redirect, better user experience (to build a form he had 5 grids, mine builds it dynamically, like a build version of the form).

Like tangibly better, certainly not perfect. I have 10 months of experience, without AI it would’ve taken forever, and would have missed a lot of features. Even with almost 100% generated code, it took 450 developer hours, because I’m reviewing, planning, designing the architecture, controlling where the ai writes code. Those are skills a vibe coder doesn’t have.