Ruby On Rails Best Practices

This extracts the architectural patterns Basecamp uses in production Rails apps like Fizzy and Campfire. You get 16 rules covering where to put concerns (scoped under models, not in a shared folder), how to name them (behaviors get -able suffixes), keeping jobs and controllers thin by pushing logic into models, and when to use resource controllers instead of custom actions. The template method pattern for shared concerns is smart, and the guidance on explicit Turbo broadcasts from controllers instead of callbacks will save you debugging time. Most valuable if you're tired of Rails codebases that feel organized differently in every directory and want opinionated conventions that scale.