Guidance on how to break down problems and structure solutions.
"Tell, don't ask" is easy to say, but how do you actually put it into practice?
Simplify baroque domain models by flattening hierarchies of reuse.
Some pointers on making your Ruby parameter defaults self-documenting.
Learn how to break a dependency on a pervasive mixin.
Learn how to present a natural interface to client code, while hiding implementation architecture details.
If you've done much Rails coding, you've probably heard the guideline: “skinny controller, fat model”. But achieving this can be easier said than done. Especially when your controllers are bloated with …
Learn how to model a system where an object may only exist in one collection at a time.
When is a Value Object not a Value Object?
Learn two ways to avoid switching on nil in Rails apps, in this double feature from RubyTapas and Upcase