dhh-rails-style

Rails code following 37signals conventions: REST purity, fat models, thin controllers, and clarity over cleverness. "The best code is the code you don't write. The second best is the code that's obviously correct." Vanilla Rails is plenty: What they deliberately avoid: Development Philosophy: Specify a number or describe your task. After reading relevant references, apply patterns to the user's code. Verbs: card.close , card.gild , board.publish (not set_style methods) Predicates: card.closed? , card.golden? (derived from presence of related record) Concerns: Adjectives describing capability ( Closeable , Publishable , Watchable ) Controllers: Nouns matching resources ( Cards::ClosuresController ) Scopes: Instead of custom actions, create new resources: State as Records: Current Attributes: Authorization on Models: All detailed patterns in references/ : Code follows DHH style when: Important Disclaimers: - Applies DHH style patterns including CRUD controllers, state-as-records instead of booleans, and Current attributes for defaults - Covers controllers, models, views, architecture, testing, and dependency decisions with specific naming conventions and code examples - Emphasizes vanilla Rails over gems: Minitest over RSpec, fixtures over factory_bot, Solid Queue over Sidekiq, database over Redis - Includes REST resource mapping patterns, concerns for horizontal behavior,...