Short Screencasts of Gourmet Ruby, by Avdi Grimm
Objects that represent the meaningful quantities of a real-world domain. These values (values like currency, calendar period or telephone number) carry whole, useful chunks of information from the user-interface to the domain model.
– adapted from Ward Cunningham in
The CHECKS Pattern Language of Information Integrity
Previously, guest chef Corey Haines joined us to talk about representing complex structured data with custom attribute types in Rails. Today, he returns to show us how to implement polymorphism …
Sometimes model attributes need to have more structure than a simple string or number. In part 1 of a 2-part series on ActiveRecord polymorphic attributes, guest chef Corey Haines demonstrates …
In this long-requested episode, guest chef Justin Weiss returns to teach you how to integrate the Whole Value pattern into Rails applications.
This page is just for members. Sign in or subscribe to gain access! Username Password Remember Me Forgot Password
How do we name a class when we're not sure how broad a category it represents?
Some domain concepts are easier to spot than others. Today we deal with one of most slippery concepts of all.
Having model attributes at different levels of abstraction can quickly complicate an application. In this episode, we'll level the playing field.
In which we examine some of the pitfalls of handling badly-formed user input for Whole Value fields.
In this episode, we address the Primitive Obsession code smell with a lesser-known design pattern.
Today, in part 1 of 2, we explore the implications of a common code smell.
