rails-37-style-philosophy-what-they-avoid

37signals avoids Devise for authentication to maintain control over their codebase, preferring custom code over relying on external gems. This approach aligns with their philosophy of building rich domain models and minimizing dependencies.

37signals deliberately avoids service objects and form objects, preferring rich domain models instead. They consolidate business logic directly within models to keep the architecture simpler and avoid unnecessary abstractions.

Instead of Sidekiq, 37signals uses Solid Queue for background processing. They also prefer Turbo and Stimulus over frontend frameworks and native CSS over Tailwind CSS to reduce dependencies.

No, 37signals avoids RSpec and FactoryBot. They prefer Minitest and fixtures for testing, keeping their testing stack lightweight and closely aligned with Rails defaults.

37signals avoids Pundit and CanCanCan, preferring model predicates for authorization. This method keeps authorization logic directly within the domain models rather than separating it into distinct objects.

Avoiding ViewComponent and GraphQL means relying on view helpers, partials, and REST. This limitation is a deliberate choice to reduce complexity and stick to standard Rails conventions over adopting popular architectural patterns.