dhh-rails-style

To write idiomatic Rails code following 37signals conventions, enforce REST purity, maintain fat models and thin controllers, and track state via database records rather than booleans. This minimalist approach eliminates unnecessary gems and external services like Redis.

The best way to review Rails code for over-engineering is to check alignment with 37signals patterns: ensure RESTful controllers, database-backed state tracking, and minimal gem usage. Code should favor built-in Rails mechanisms over external service dependencies.

Hotwire fits into the 37signals Rails architecture by utilizing Turbo and Stimulus frontend patterns alongside native CSS. This approach maintains a minimalist, database-backed architecture by reducing the need for heavy JavaScript frameworks and external frontend state management.

You do not need Redis or Sidekiq for background jobs in a minimalist Rails codebase aligned with 37signals conventions. The preferred approach uses database-backed solutions for state tracking and background processing to avoid external service dependencies.

Basecamp and HEY style patterns favor Minitest and fixtures over RSpec for testing Rails code. Aligning with 37signals conventions means adopting Minitest workflows to maintain the minimalist, production-tested standard used in their real-world codebases.

You should avoid database-backed state tracking in Rails when your application requires high-throughput, ephemeral state management that genuinely necessitates external services. However, for standard application workflows following 37signals conventions, database records are the preferred minimalist solution.