Exploring Alternatives

Comparing design approaches means generating 2-3 viable alternatives, documenting their trade-offs against criteria like simplicity and performance, then selecting the simplest approach that meets your requirements. This prevents costly implementation mistakes by exploring options systematically before writing code.

Explore alternatives for non-trivial features, complex algorithms, system design decisions, refactoring, architecture choices, and data-structure selections. For routine tasks, direct implementation is fine; for decisions with broad impact or uncertain tradeoffs, systematic exploration saves rework.

Document trade-offs across simplicity, performance, maintainability, and any domain-specific criteria relevant to your problem. Comparing alternatives side-by-side against these dimensions surfaces hidden costs and helps you choose the approach that best fits your actual constraints, not assumptions.

Best fit depends on your specific requirements and constraints. Compare candidates against criteria you define—simplicity often wins for long-term maintenance. Evaluate each alternative's tradeoffs, then select the simplest one that satisfies all your requirements rather than the theoretically optimal one.

This approach applies equally to refactoring and new features. Explore alternative refactoring strategies—preserving existing behavior, incremental migration, or full replacement—and compare their tradeoffs before committing to one path.

Exploring alternatives is systematic: generate 2-3 concrete options, document their tradeoffs, and decide. Overthinking lacks boundaries. Set a limit on alternatives upfront and commit to a decision once you've compared them against your criteria.