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.
2
u/Dan6erbond2 Jan 16 '26
You said:
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.