One reasonably high-effort way is to make it more modular and testable by splitting things out into middlewares with Coach:<p><a href="https://gocardless.com/blog/getting-started-with-coach/" rel="nofollow">https://gocardless.com/blog/getting-started-with-coach/</a><p>I’ve worked in this team’s codebase and can confirm it has a rather nice DX, even as a new joiner with a python background.<p>——<p>Who are the people who want to improve the developer experience?
RubyMine to keep your sanity - in large codebases rails is terrible with ambiguity. You don't know what a variable is, if it's a function, a method in the class, a helper imported, what.<p>Then leverage the test suite to understand what something is supposed to do, naming conventions only take you so far especially if the team wasn't really disciplined about it.
I've found that great, modern IDEs (like those made by JetBrains for various languages) have vastly better support for static analysis and, therefore, refactoring.<p>What IDE are you using?<p>Other than that, running integration tests from outside that code base can at least help you catch errors early.
Maybe watch some Sandi Metz talks together as well as Ben Orenstein’s refactoring talk and then see if you can align around some practices that you think could make your lives easier.<p>Code styleguide is another possible direction.