Reaction

The limits of '$ per review' as a code-review metric

A developer says their internal system catches more bugs upfront than Greptile, which they also use.

1 Source, 21m ago, first seen 21m ago

TLDR

A developer who runs Greptile alongside an internal code-review system calls Greptile impressive but says their own system catches more bugs and issues upfront, with greater correctness. They dispute Greptile's '$ per review' metric, arguing that it misses the extra PRs created as Greptile reveals new bugs incrementally. They consider '$ per PR' a better, though still imperfect, measure.

Combined views

—

1 Source, first seen 21m ago

— likes— comments— saves— reposts

Reaction

The limits of '$ per review' as a code-review metric

A developer says their internal system catches more bugs upfront than Greptile, which they also use.

1 Source, 21m ago, first seen 21m ago

TLDR

Today's Rank

—

Not ranked yet

Combined views

—

1 Source, first seen 21m ago

— likes— comments— saves— reposts

Sentiment

Positive——Negative

Summary

Not enough discussion yet.

No sentiment analysis available yet.

Featured Source

JR JD Ross@justindross 2:23 PM · Oct 13, 2026
We run greptile in parallel and it is impressive... but we built our own Code Review system and we like it more. I think their "$ per review" measurement is bullshit. If you use Greptile you'll create more PRs because there's more bugs, and it keeps revealing novel bugs…