dhh-rails-reviewer

Reviewing Rails code for convention over configuration involves analyzing your application to ensure it follows standards like fat models, skinny controllers, and RESTful routing. This identifies deviations from Rails conventions and flags unnecessary abstractions like service objects or presenters.

Common JavaScript framework anti-patterns in Rails applications include unnecessary API layers, JWT token implementations, and Redux-style state management. Identifying these patterns helps maintain Rails' idiomatic approach and avoids introducing unnecessary complexity into your monolithic architecture.

Service objects and presenters often represent unnecessary complexity in Rails apps. Analyzing these abstractions through a convention-over-configuration lens reveals whether they add value or simply deviate from the majestic monolith philosophy by over-engineering standard Rails components.

To check if a Rails feature aligns with DHH's simplicity philosophy, evaluate its adherence to convention over configuration and the majestic monolith approach. This identifies over-engineering, JavaScript-world patterns, and unnecessary architectural layers that contradict standard Rails idioms.

You should not use hexagonal architecture in your Ruby on Rails application when it introduces unnecessary complexity and deviates from standard Rails conventions. This architectural pattern often conflicts with the majestic monolith philosophy by adding abstract layers where standard components suffice.