approach-evaluation

To compare technical approaches, research industry best practices to identify 2-3 viable solutions and evaluate them against project-specific constraints. This structured comparison surfaces trade-offs and open questions, reporting options without making a decision.

Evaluating architectural decisions requires resolving project context and prior decisions from memory to define criteria. You then assess identified approaches against these specific constraints, clearly outlining the gains, costs, and operational implications for your existing stack.

Researching industry best practices for technical decision making involves gathering information on current standards to identify 2-3 practical solutions. You then assess these options against defined criteria to produce a factual comparison of viable architectural approaches.

Yes, a structured comparison objectively assesses options against project-specific constraints to surface trade-offs and open questions. It explicitly reports the findings without making a decision, leaving the final architectural choice to a human.

Yes, technical evaluation resolves project context, patterns, and prior decisions from memory before comparing approaches. This resolution defines the evaluation criteria needed to accurately assess stack compatibility, operational fit, and maturity.