dhh-rails-style

To refactor Rails code toward DHH conventions, enforce thin controllers and fat models by moving business logic into models, mapping to RESTful CRUD resources, and replacing boolean columns with state-as-records. This approach prioritizes vanilla Rails clarity over clever abstractions.

37signals conventions for Rails routing and state management require strict RESTful CRUD mapping, including singular resources, and tracking state-as-records rather than using boolean columns. This ensures database-backed solutions maintain clarity and maintainability over clever architectural abstractions.

DHH style Rails prefers a Hotwire-first pattern using Turbo and Stimulus for view and frontend interactions over heavy JavaScript frameworks. This approach keeps the implementation aligned with vanilla Rails architecture and maintains clarity over clever abstractions.

Writing Rails tests following 37signals conventions requires using Minitest with fixtures rather than RSpec and factories. This testing norm aligns with the vanilla Rails philosophy, ensuring tests remain clear and maintainable without relying on clever abstractions or extensive additional dependencies.

Handling Rails authentication and background jobs in DHH style involves using Current attributes and standard Rails architecture patterns. It prefers database-backed solutions and vanilla Rails conventions over external gems, ensuring clarity and maintainability throughout the application design.

You should avoid boolean columns in Rails models when following DHH conventions, replacing them with state-as-records to track status. This approach treats state as a first-class database record, improving clarity and maintainability while preventing scattered conditional logic across your application.