dhh-rails-style

To write Ruby on Rails controllers following DHH's coding style, keep controllers thin by pushing business logic into fat models, use Current attributes for global state, and prioritize clarity over cleverness to avoid unnecessary abstractions.

DHH's conventions for REST and architecture in Rails applications emphasize REST purity in routing, using Hotwire patterns for views, and selecting specific database and job patterns to ensure pragmatic and maintainable application structures.

Yes, you can use this to review and refactor existing Ruby code against 37signals conventions by auditing your codebase for deviations from DHH's patterns, ensuring your models, controllers, and testing align with his preferred approaches.

You should avoid clever abstractions in Rails code generation when a simpler, Rails-native solution exists, adhering to the clarity over cleverness philosophy championed by DHH to ensure your code remains clean and maintainable.

Yes, DHH's Rails style guide includes guidance on gem selection and testing, providing recommendations on preferred approaches for routing, authentication, jobs, and database patterns based on analyzed production codebases.