A talking rubber duck can question assumptions, propose competing hypotheses, and suggest experiments instead of merely forcing you to explain the bug aloud.
Start with observed facts, expected behavior, and one testable hypothesis. Ask the assistant what evidence would distinguish that idea from alternatives, then run the smallest useful experiment.
Guard against anchoring on a fluent story. Share only relevant, redacted logs, and verify claims in code, documentation, or runtime output. The assistant expands the search space; direct observation decides which explanation survives.
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
Why there's no diagram: “”
The interactive diagram is below the answer - jump to diagram ↓ · Below it, the related concept . Jump to it ↓
The diagram below the answer is the concept . Jump to it ↓