Chapter 38. Monoliths “Unstrung,” Part 2: Refactoring
“All for one, and one for all” might work for musketeers, but it doesn't work nearly as well for class designers. Here's an example that is not altogether exemplary, and it illustrates just how badly you can go wrong when design turns into overdesign. The example is, unfortunately, taken from a standard library near you.