Comment by willahmad
17 hours ago
> This is why we assign an engineer to review every PR of a vibe coded project and they don’t really need all of the context to detect bs approaches that will surely fail.
I see this trend in many companies as well, just curious, how do you make sure engineering time is not wasted reviewing so many PRs? Because, some of them will be good, you only need couple of your bets to take off, some definitely bad
Its commonly understood that whoever is reviewing the PR shouldn't concern themselves with all of the project’s context (business or any other).
It really takes a glance at the PR to see what the author wanted to create and you can pick up on bad directions the AI took and so you just help the person navigate these choices.
Of course if the project has to actually grow into a product at some point you would have to rewrite good chunks of it.