dhh-rails-style

DHH's Rails style enforces thin controllers by moving business logic into fat models and adhering to strict REST resource mapping. This approach prioritizes REST purity and leverages vanilla Rails capabilities for cleaner code architecture.

DHH's Rails best practices advocate for fat models to encapsulate business logic and maintain REST purity. The philosophy emphasizes clarity over cleverness, ensuring models handle core domain rules while controllers remain thin routing layers.

Hotwire fits the 37signals Rails style by using Turbo and Stimulus patterns to build interactive frontends without complex JavaScript frameworks. This approach maintains the clarity over cleverness philosophy while leveraging vanilla Rails capabilities for UI updates.

Current attributes in Rails should be used to manage global request-specific context like the authenticated user. This pattern aligns with DHH's pragmatic style by cleanly passing request-level data throughout the application without cluttering method signatures.

This approach works for both existing Rails code reviews and new code generation. The conventions trigger during refactoring requests and code reviews to ensure existing logic adheres to 37signals patterns like REST purity and clarity over cleverness.

The core philosophy behind Basecamp and HEY's Rails architecture is clarity over cleverness. It champions vanilla Rails, fat models, thin controllers, and Hotwire patterns to achieve pragmatic, efficient, and maintainable application structures.