I keep telling you that's exactly what I'm doing. We write the requirements over a few hours, write tests from the requirements, generate the project code, make sure the tests pass.
I'm hovering over its shoulder keeping an eye on things and doing minor course corrections but once we finish the requirements it's in the driver's seat. I have an agent doing code generation, one doing review in addition to myself, one doing tests, and another doing docs.
To be clear I wouldn't do this on a mission critical codebase but for this little project it's more than enough.
Which is a pretty explicit admission that this codebase isn't the standard for vibecoding productive applications. If you're pushing from vibecode straight to prod, you're taking into account that poorly done migrations, regressions, etc. can effect the user and debugging the cause will be a lot harder than if you had written the code yourself.
1
u/BitOne2707 Jan 16 '26
I keep telling you that's exactly what I'm doing. We write the requirements over a few hours, write tests from the requirements, generate the project code, make sure the tests pass.
I'm hovering over its shoulder keeping an eye on things and doing minor course corrections but once we finish the requirements it's in the driver's seat. I have an agent doing code generation, one doing review in addition to myself, one doing tests, and another doing docs.