debugging

Systematic debugging follows a structured workflow: understand the problem by reproducing it, gather information from logs and traces, isolate the root cause through targeted inspection or binary search, apply a fix, and verify it with regression checks. This protocol accelerates diagnosis across development environments.

Inspect logs and traces by running commands to examine error output, stack traces, and recent code changes. Targeted logging reveals code paths and state at failure points. Cross-reference logs with code changes to narrow down where the bug was introduced.

Use binary search or targeted logging to isolate bugs. Narrow the scope by testing specific code paths, disabling features incrementally, or adding logging at suspected points. Reproduce the issue consistently first to confirm the conditions that trigger it.

Yes, the structured debugging workflow applies across development and production environments. Adapt information-gathering commands and logging patterns to each environment's tools and access constraints while following the same problem-understanding and isolation steps.

After applying a fix, run regression checks to confirm the original issue is resolved and no new problems appear. Test the specific code path that was broken, then run broader test suites to detect side effects in related functionality.

Document the expected vs. actual behavior, steps to reproduce, relevant logs and error traces, the isolated root cause, the fix applied, and regression test results. This record supports future troubleshooting and helps teammates understand the issue and resolution.