This article is part 6 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. (If you missed the start of this series you can catch up with part 1 here.)

Last time, I decoupled the code from the prices of A and B.

Thanks for reading Habitable Code! Subscribe here to see how this worked example p...