Thread

There is more to code review than (automatable) detection

165 points · 117 comments · utiiiD

bob1029 · 1790582589 · focus · HN ↗
One of my clients has an automatic "best practices" AI robot that runs each time you create a PR. It is pure downside. Even the developer responsible for creating it admits as much.
However, for some weird reason it's still in place. This is the part that actually concerns me. Ignoring the bullshit comment is trivial. The quiet and relentless accumulation of entropy is happening everywhere. This is why GitHub crashes at noon every business day.
1. crazybonkersai · 1790583045 · focus · HN ↗
  This does not reflect my experience. AI code review has improved tremendously in the last years to the point that nobody in my team does manual code review any more. It used to be ridiculously bad two years ago, but not any more.
  1. griffiths · 1790583426 · focus · HN ↗
    Do you use some "framework" specifically or (custom) skills, or is it just plain prompt to review the code?
    crazybonkersai · 1790584154 · focus · HN ↗
    At a workplace we have a review skill which includes things like skipping nitpicks and trivial issues. Myself I just use a simple prompt, as well as Copilot review on Github. There is a school of thought to use a different model for a code review and code generation, but I have no opinion about that.

Unofficial Hacker News client; not affiliated with Y Combinator.