Setting up Rubocop on a new Rails application will get you on the path towards a well-maintained codebase. But what if you have an older project?

When you set up Rubocop on an existing application, it’ll likely show you hundreds or thousands of issues the first time you run static code analysis. That’s enough to get developers to abandon the plan to use Rubocop to improve their app.

Instead of getting overwhelmed, here are a few tips you can use to chip away at those issues to reduce those Rubocop offenses quickly and get your old Rails codebase clean and organized for long-term maintainability: https://youtu.be/PsXnIBe2kqw