Loading page content
Explaining a problem out loud, one step at a time, is often all it takes to find the bug. This duck listens and asks the annoying-but-useful questions a senior engineer would.
Rubber duck debugging is real: explaining a problem out loud, step by step, is often enough to spot the bug. This duck listens, asks the annoying-but-useful questions a senior engineer would, and never tells you to read the docs. No AI, no server: it's a duck.
Tip: say "fixed" when you find it. Out of excuses? Try the Developer Excuse Generator. Real errors: Claude Code errors, fixed.
100 of 102 run entirely in your browser (Weather Widget uses Open-Meteo; What's My IP asks this site's server).
Share on XShare on LinkedInRubber duck debugging comes from The Pragmatic Programmer: a programmer explained their code line by line to a rubber duck and found the bug along the way. Putting the problem into words forces you to check the assumptions you skipped while reading the code.
This duck adds prompts. It recognizes common bug patterns (errors, environment differences, things that 'suddenly' broke, timeouts, nulls, async ordering, stale caches, DNS) and asks the question that usually cracks them. There's no AI and no server; the conversation stays in your browser tab.