Stripe merges ~1,300 PRs a week with no human-written code. Spotify has merged 1,500+.

The bottleneck isn’t writing code anymore. It’s trusting it.
For Android, that matters even more: a bad change can stay on users’ devices until they update.

In this talk, we’ll look at how to make a codebase cheap to trust, so review isn’t the only thing standing between a bad change and production.

We’ll cover:
1. Gates — checks nobody can skip
2. Budgets — recomposition, APK size, and other hard limits
3. Boundaries — modules that enforce where code can go
4. Blessed paths — convention plugins that make the right thing the default

The goal: make correctness a property of the system, not a job left to the reviewer.