Programming is hard, but sometimes we can overcomplicate things for ourselves. Join guest Chris Doyle to learn why a problem that feels "TOO HARD" is a code smell, and what …
In which we examine some of the pitfalls of handling badly-formed user input for Whole Value fields.
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?
Today, in part 1 of 2, we explore the implications of a common code smell.
An argument for why same things should look the same.
As we continue examining code smells in mockist tests, today we turn our attention to code that mocks out core I/O calls.
Some more indications that you might not be using Mock Objects to best advantage.