Architecture & practice·Judgement and reasoning traps
you explained the bug out loud to a colleague and worked out the answer before they said anything.
Rubber duck debugging
Explaining a problem step by step to someone or something else, which forces the gaps in your reasoning to surface. It works because narrating requires making every assumption explicit, and the wrong one usually announces itself when spoken. It is worth naming because it makes asking for help cheap: the request is for two minutes of attention, not for an answer.