It looks to me that the author has not faced a problem with DRY, but a junior developer and/or YOLO approach to architecture design. In many cases thinking abo

It looks to me that the author has not faced a problem with DRY, but a junior developer and/or YOLO approach to architecture design. In many cases thinking about possible future features/extension was one of the most limiting, complexing and at the end irrelevant approach out there, because it usually turned out that the future was different than it had been imagined. On the opposite side, when you take into account just what you know at the time of writing, led to easier adjusts, because it was way more clear to understand. DRY is a great technique to organize your code, you just need to think about the structure first. In this article, the problem was that he wanted to bend 2 pizzas method into many other different types of pizzas, so his pizza architecture changed so vastly that it was not possible to describe it with just the initial idea of pizza.