research

Systematic technical research involves defining clear research questions, identifying authoritative sources, extracting key information, validating findings across multiple sources, and synthesizing results into actionable implementation plans. This approach ensures decisions on architectures, tools, and scalability are evidence-based and maintainable.

Evaluate source credibility by assessing the author's expertise, publication venue reputation, recency of information, potential bias, and relevance to your specific use case. Cross-referencing findings across multiple independent sources strengthens confidence in your conclusions.

Synthesize by identifying common patterns and themes across sources, noting areas of agreement and disagreement, extracting key concepts, and organizing findings into structured sections addressing your original research questions. This produces actionable insights rather than disconnected facts.

Yes. Structured research methodology supports comparative analysis by systematically gathering requirements, evaluating each option against defined criteria, documenting trade-offs, and validating claims through multiple sources. This produces justified recommendations aligned with YAGNI, KISS, and DRY principles.

Gather performance benchmarks, security track record, community maturity, maintenance status, integration compatibility, scalability limits, and real-world implementation case studies. Phase-based scoping ensures you collect only relevant data for your specific phase—proof of concept, development, or production.

Critical thinking prevents accepting biased or outdated claims uncritically. It involves questioning source motivations, identifying gaps in evidence, recognizing evolving best practices, and connecting findings to your constraints. This rigor produces decisions resilient to future change.