How Brex prevents bugs in a nearly decade-old monorepo with Greptile

I personally spent a lot of time commenting on PRs telling people to follow our well documented best practices. With Greptile custom rules, I was able to reduce my time spent reviewing standard practices and allow Greptile to enforce them for me across the company.

Other tools struggled with our eight-year old monorepo and technical stack. Their feedback was generic and didn't seem to really understand our codebase. Greptile was the only tool that really caught issues and provided context-aware feedback. Building an equivalent system internally would have taken far longer and ultimately been more expensive.

I primarily care about two things: quality and throughput. Having a tool that sits between traditional static tooling and human reviewers eases the burden and allows us to move faster through increased confidence in our quality on smaller changes freeing up more time for the more complicated aspects. We use Greptile's mermaid diagrams and confidence scores as a proxy for how complicated individual pieces of code are, before going deep on it. When confidence is high, and the flow is simple, we move faster; when it's low or the diagram is convoluted, we add expert reviewers and dig deeper. That shortens reviews on straightforward changes and reduces risk on nuanced ones.