jr-debug

Evidence-based debugging is a systematic approach that transforms vague issue reports into testable hypotheses supported by data. Use it for complex software issues, log analysis, and configuration problems where the root cause is not immediately obvious.

To create a structured debugging plan, describe the issue to generate initial hypotheses and evidence-based tests. This workflow ensures each conclusion is supported by evidence and documented, progressing from vague failure reports to reproducible plans.

Investigate performance anomalies by forming rigorous hypotheses and planning tests based on system evidence. This method applies structured steps to isolate root causes in logs and configurations, escalating to implementation only when verification requires it.

The best way to document troubleshooting resolutions is by recording each step of an evidence-based investigation. This ensures every hypothesis, test result, and conclusion is reproducible and clearly mapped from the initial issue report to the final fix.

Yes, this approach supports configuration problems and log analysis where root causes are not immediately evident. It guides you through rigorous hypothesis formation and test planning to verify issues across complex software systems.

You should escalate from investigation to implementation after verifying your evidence-based hypotheses. The workflow supports escalation when necessary, ensuring you only implement fixes once the root cause is confirmed through structured, reproducible tests.