3 ms·
My experience with these Vibe Review tools has been pretty mixed. Fundamentally, they are doing 2 things: 1. reordering the hunks in a "more relevant" order (i
by RomanKornev 14d ago
My experience with these Vibe Review tools has been pretty mixed. Fundamentally, they are doing 2 things:
1. reordering the hunks in a "more relevant" order (instead of alphabetical)
2. adding some "fluff text" to connect the hunks together in a narrative
In practice, the reordering doesn't shorten the review time that much (and extends it greatly when the order is illogical), and the AI "explanations" rarely add value. The second video's Review Guide in TFA is way longer than the diff itself.
I much prefer the strict 2-pane setup with rationale and diff strictly separated, and the "self-review" author comments in the diff provide the context for reviewers.
Other similar attempts at this UI this year:
- by Graphite https://graphite.com/blog/code-tours https://graphite.com/blog/code-tours (April)
- and CodeRabbit https://www.coderabbit.ai/blog/introducing-change-stack-the-first-ai-native-code-review-interface https://www.coderabbit.ai/blog/introducing-change-stack-the-... (May)
Is this seriously supposed to replace Pull Requests?
- mhh__ 14d agofrankly i think most of these "tools" are the result of people being addicted to watching the agent shit code out and as such quietly abolishing review.
- RomanKornev 14d agoThere's tons of good ideas on how to improve the code review, but for some reason everyone just gravitates to the most basic "copilot" experience. I'm sure by next year someone will finally figure out a better flow.