Vibe coding is collapsing the distance between idea and deployment. But the real risk is whether your company has the judgment system to govern what AI can now build.
We inadvertently let two Jr’s vibe code a project. They used their own Cursor subs and did not tell anyone. They are no longer with us. Now there is this project with no documentation, they removed the LLMs comments, and then ran a linter. I checked the git history. Nobody can make sense of the code base. We can’t even empirically show that it is cheaper to rewrite than start over, so we just stare at it everyday. Nobody can add any features. When you debug you end up in abstraction hell and work through the most buggy nonsense code.
We don’t even use Cursor. I have considered putting sections into Opus 4.6 and asking what bugs it can find for me. I have done that before with unquantifiable results.
We inadvertently let two Jr’s vibe code a project. They used their own Cursor subs and did not tell anyone. They are no longer with us. Now there is this project with no documentation, they removed the LLMs comments, and then ran a linter. I checked the git history. Nobody can make sense of the code base. We can’t even empirically show that it is cheaper to rewrite than start over, so we just stare at it everyday. Nobody can add any features. When you debug you end up in abstraction hell and work through the most buggy nonsense code.
Have you tried to ask cursor to add some new features
We don’t even use Cursor. I have considered putting sections into Opus 4.6 and asking what bugs it can find for me. I have done that before with unquantifiable results.
Cursor uses opus 4.6 by default anyway.
Just open Claude code in your case, some thing
Hey, I’m annoyed by slop coding work as much as the next guy, but murder seems a bit much as a reaction…
I only want to punch the one guy in the throat. I am not that violent.
Not to the shareholders.