Guidance on how to break down problems and structure solutions.
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 this sequel to #430, we apply a powerful pattern for encapsulating problem values.
In which we examine some of the pitfalls of handling badly-formed user input for Whole Value fields.
Sometimes we put data into a cache, only to find that things break when we try to take it back out again. Here's how to avoid this problem.
In this episode, guest chef Sam Livingston-Gray shows us how getting a new view on our data model can drive out a cleaner design.
In this series conclusion, we learn some lessons about trampolines and self-saving domain models.
This page is just for members. Sign in or subscribe to gain access! Username Password Remember Me Forgot Password
Continuing in our series, we examine three more problem scenarios with self-saving objects.
The start of a series answering the question: why shouldn't a domain model object save itself?