Guidance on how to break down problems and structure solutions.
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?
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.
In today's episode, we discuss what it means for an object to have invariant properties.