This article is part of a series in which I’m doing a well-known code kata in the “TDD as if you meant it” style. I’m also strictly following the 4 rules of simple design and looking for opportunities to use implicit coupling to drive refactoring under the Once And Only Once rule. (If you missed the start of this series you can catch up with part 1 here.)

I’m going to take a break for the next couple of weeks.

And before I do that, I want to ask you a question: Is this kata seri...