debugging

To debug hard-to-find bugs caused by asynchronous behavior or state mutations, use structured workflows like generating 3-5 hypotheses, tracing code flow, and inserting targeted logs at async boundaries to identify where expectations diverge.

Rubber ducking is a software debugging technique where you verbalize the code logic and compare expected versus actual behavior to reveal discrepancies that expose the root cause.

The best way to trace data through unfamiliar code paths is to follow the code flow systematically, tracking data through each transformation from input to output to identify exactly where expectations diverge.

To verify a failing line before applying a bug fix, trace the exact failing lines, understand why the code fails, and test your generated assumptions to eliminate false causes before making changes.

Yes, you can use agent-assisted investigation to debug complex code paths by spawning Explore agents to trace specific routes and report back, using multiple advisor perspectives when stuck.

You should insert targeted logs during systematic debugging at decision points and async boundaries to capture key states for diagnosis, ensuring you clean them up after validation.