(10+ years with Rails) The key to maintaining a healthy Rails codebase is to make most of your code independent of Rails. Rails is great at the basics: Handlin

(10+ years with Rails) The key to maintaining a healthy Rails codebase is to make most of your code independent of Rails. Rails is great at the basics: Handling requests and composing views. It's okay at storage stuff. But it's not good at handling complex usecases, managing JS, etc. This isn't to say that you can't use Rails if you're making complicated stuff, or using JS, it just means you need to know when to keep your code to Rails's structures and when to write your own structures that you then invoke from within Rails.