Skip to main content

One post tagged with "code-review"

View All Tags

Code Review at Orus

· 29 min read
Samuel Rossille
Samuel Rossille
Chief Technology Officer
Cover

Everybody who writes software with AI agents sees the same thing: code review became the bottleneck. Writing code got cheap. Reading it did not.

We saw it in our own numbers. Comparing the months after July 2026 with the quarter before, the average number of lines of code produced per person went up by 72%. The median pull request grew from 72 to 129 lines. Merged PRs per person went up too. And the median time to merge a PR went up sharply, because the people who review are the same people who now produce twice as much code.

The usual framing is a trade-off. Keep reviewing everything the way you used to, and let the team spend its days waiting for each other. Or lower the bar, and slowly lose what review was protecting: security, architecture, coding standards, and the shared understanding of the codebase.

That framing treats review as one job. It is several:

  • catching bugs before production
  • holding the code to our standards
  • guarding security and architecture
  • spreading knowledge across the team
  • on some PRs, a real design discussion between people who know the domain

Those jobs don't need the same reviewer. Checking a change against almost two hundred coding rules, or hunting for the retry that charges a customer twice, takes patience and context more than seniority. Deciding whether a design is right, or signing off on a pricing change, takes a person who owns the consequences. So we split them. Orusaurus, an AI reviewer we built in-house, does the first kind of work on any PR you ask it to review, in about four minutes. Our approval rules decide which PRs still need a human, and that is where human attention goes.

This post describes how it works, the decisions behind it, what we measured, and what it does not do. It is also the reference for our own team on what to expect from it.