Now here’s a tough problem. As a codebase grows, so does the rise...

So what do you do? We found it best to gradually migrate, or “ratchet,” older patterns over a long period of time.
Warnings pile up as they’re ignored or seen as optional, burying important issues, so we do not allow any ESLint warnings in our code.
We only allow lint rules to report as errors. If the error is specifically allowed by the ratcheting system, they are downgraded to warnings.
We love this chart:
So, this is what we came up with. We switched to a tab-separated value (TSV) format that keeps entries atomic + independent while keeping readability.
Each line tracks how many errors are allowed for each error combo.
Well, we feed data from the ratchet file into both Notion + Datadog. This shows us how quickly we’re eliminating outdated patterns and where we might need to focus our efforts.
Integrating with Notion is super important to make the data accessible to non-engineers.
Alright. Here’s how it works:
We first create ESLint rules to spot bad patterns. For simple violations, we write an autofixer.
For more advanced violations, we offer guidance to developers through descriptive error messages as they work around the violating code.
We found it provides just enough developer friction to uphold our high standards over time. Using the ratcheting system, we have executed many complex migrations.
Even though this makes it slightly more difficult to reorganize the codebase because we have to keep updating the ratchet file, we think this is a worthwhile trade-off.
github.com/justjake/eslin…
Looking for more? Dive into the details on our Tools and Crafts blog.
Read here: notion.com/blog/how-we-ev…








