Today we learn an alternative to "service objects" for scripting user interactions.
In this follow-up to episode #331, we examine how naming methods can alter how responsibilities are distributed.
In this series conclusion, we learn some lessons about trampolines and self-saving domain models.
The start of a series answering the question: why shouldn't a domain model object save itself?
Today we put on our philosopher hats, and talk a little about what makes an object a process.
Today we begin a conversation about Service Objects and alternatives.
Treat your objects as disposable to cut down on mutable-state-based bugs.