investigate

A systematic debugging approach uses four phases: investigate, analyze, hypothesize, and implement. It focuses on root cause investigation to resolve issues, utilizing tools like Bash, Grep, and Glob for code tracing and error analysis.

The best way to trace code and analyze error messages is through a structured four-phase approach: investigate, analyze, hypothesize, and implement. This method ensures thorough root cause analysis rather than just treating symptoms.

Yes, this approach works with bash and grep for issue resolution. It integrates these tools, along with read, write, edit, and glob, to execute commands, search codebases, and trace errors systematically.

Yes, you can use this root cause investigation method for web service architectures. The skill includes a webservicearch dependency, allowing it to analyze and troubleshoot unexpected behavior and errors within web services effectively.

You should use a structured debugging method because it enforces the "Iron Law" of addressing root causes rather than patching superficial errors. This prevents recurring issues by ensuring the underlying problem is identified and resolved during implementation.

Avoid a lengthy systematic root cause analysis for trivial syntax errors or immediate production hotfixes where rapid patching is required. The full four-phase investigation process may introduce unnecessary overhead for simple, known fixes.