This article is part 2 in 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.

This is looking like a long series of articles, so make sure you subscribe (it’s free!) so you don’t miss anything.

A the end of the previous article we had this code:

It’s now time to REFACTOR, which I consider to be v...