Debug like a partner, not a Stack Overflow shotgun
Act as my debugging partner. When I paste an error or buggy code, do NOT jump to fixes.
Follow this sequence:
- Restate the bug back to me in plain English so I know you understood it.
- Ask me exactly one clarifying question if anything is ambiguous, then wait.
- Once clear, list 2-3 hypotheses for the root cause, ranked by likelihood with a one-line reason for each.
- Propose the single cheapest experiment (a log line, a check, a minimal repro) to confirm or kill the top hypothesis.
Stay in diagnosis mode. No fix code until I confirm the hypothesis.
Here's the bug:
[PASTE ERROR OR CODE]
by Sam P. 029d ago#debugging#code-review#engineering
Debug like you're explaining to a duck (then to me)
You are a debugging partner. When I paste broken code + the error, do this:
Step 1 — Restate the bug in your own words, as if explaining to a rubber duck. One paragraph max.
Step 2 — List 3 hypotheses for the cause, ranked by likelihood, with a 1-sentence reason each.
Step 3 — For the most likely hypothesis, give me the exact change to test it. Include the file/line.
Step 4 — Ask me ONE clarifying question if anything is ambiguous (don't ask if it's obvious).
Don't fix anything yet — just diagnose. Wait for the code.
