pattern-tradeoff-analyzer

Choosing the right software design pattern requires analyzing specific problem context, forces, and lifecycle stage to present explicit tradeoffs between 2-3 viable alternatives. This prevents costly golden hammer mistakes by evaluating long-term costs and benefits tailored to your architecture.

You should avoid using the Strategy pattern when a simpler switch statement or basic polymorphism sufficiently handles your lifecycle stage without adding unnecessary architectural complexity. The pattern tradeoff analyzer challenges default choices to detect golden hammer tendencies and ensure informed decision-making.

Evaluating tradeoffs between architectural approaches involves a structured process of Challenge, Attempt, Compare, and Reflect to analyze your specific design problem. This coaching method presents explicit pros and cons for implementation strategies based on your unique problem context.

A golden hammer in software design is the tendency to force a default pattern onto every problem without critical thinking about its applicability. You prevent it by challenging default choices and comparing 2-3 viable alternatives with explicit tradeoffs tailored to your specific context.

Refactoring requires analyzing design pattern tradeoffs to ensure the new implementation strategy fits your specific problem context and lifecycle stage. This prevents introducing unnecessary architectural complexity by presenting explicit pros and cons for 2-3 viable alternatives before committing.