Maintaining Rails code with best practices in a growing codebase
Rails is an incredibly powerful framework, but maintaining Rails code becomes unwieldy as it outgrows its basic structure. Once your business logic becomes more complicated than a straightforward mapping between one controller action and one database row or table, it's hard to know what Rails best practices are — there's little guidance for large codebases.
Our Rails for Larger Codebases workshop will walk you through Rails architecture best practices so you can learn how to keep the best parts of Rails as you grow. We'll teach you how to solve for the Rails problem with growth by moving complex business logic into plain Ruby objects that interact with Rails.
In this workshop, Noel Rappin, author of several books on Rails development, will share his Rails coding best practices for managing more complex applications. He'll also walk you through how to add newer abstractions that allow your code to grow without losing the best of Rails.
You’ll learn why it can be effective to move your business logic out of Rails and into plain Ruby objects that interact with Rails — and how to do it. You'll also get a chance to see how logic objects can robustly handle increased complexity and changes in requirements.
Noel Rappin is our principal software engineer — he helps us build products, leads the apprenticeship program and hosts the Tech Done Right podcast. On his own time, he’s the author of multiple books on development best practices, including Rails 5 Test Prescriptions and Take My Money: Accepting Payments on the Web.
Noel also has a Ph.D. in educational technology and user-centered design, and while we tease him about being Dr. Noel, we’re lucky to have his mind on our team — and to be able to share it with others.