design-patterns

Choose design patterns by evaluating the specific axis of change in your code. This framework selects creational, structural, or behavioral patterns based on whether your refactoring targets extensible architecture, modularity, or complex conditional logic reduction.

You need a state machine or strategy pattern when refactoring complex conditional blocks that recur and require modularity. This approach validates pattern application against the axis of variation to ensure it simplifies logic without adding unnecessary abstraction.

Detect unnecessary abstraction by validating pattern application against the principle of least complexity. This approach identifies when singletons, abstract factories, or other patterns introduce over-engineered indirection without a specific recurring problem justifying the added complexity.

Applying design patterns does not always improve code quality if the added indirection lacks a specific recurring problem. This approach ensures patterns are applied only when they justify their complexity, preventing over-engineering while targeting improved extensibility and modularity.

Refactor a class hierarchy by evaluating structural design patterns against your specific axis of variation. This approach suggests a more maintainable structure that improves modularity and extensibility while adhering to the principle of least complexity to avoid unnecessary abstraction.