Pattern Fever: When a Pattern Makes Code Worse
A pattern is a fix for a problem, so a pattern with no problem to fix (a factory for a factory, a strategy with one choice, an interface with one class that will never have another) is pure cost: more classes and more jumps for no change made easier; the cure is the simplest thing that works, and the pattern comes back when its problem does.
Updated

- Category
- Data Structures
- Level
- Journeyman
- Tags
- Design Pattern, OOP, Over-Engineering, software-development, YAGNI