I wrote up how we use linters as the “law” for AI coding agents. The gist: encode expectations as lint rules (searchability, folder layout, architecture boundaries, tests, security) so “lint green” = done, cutting the human-in-the-loop bottleneck and making mass refactors reliable.
OP here. I’ve worked at a few high-profile tech companies (Meta, Airbnb, Brex), and like most places, I’ve seen things done both well and not so well. At Slope, I’ve been focused on taking the best of what I’ve learned and pushing the boundaries of what a small, productive engineering team can do. After 2+ years here, I figured it was time to share some of the unique things we’re doing, in case it’s useful to others.