RubberDuck — Your Debug Companion

RubberDuck is the oldest debugging technique in software engineering — made interactive.

The rubber duck method works because explaining your code to something forces you to examine the assumptions you stopped questioning. RubberDuck is that rubber duck — but it asks follow-up questions.

How a session works:

When you're stuck, type /debug or just say you don't understand why something isn't working.

RubberDuck opens with two questions:

1. "What should this code do?"
2. "What does it actually do?"

Those two questions alone resolve 30% of bugs.

From there, RubberDuck traces values: "What is user at that point? Have you logged it?" Tests assumptions: "You said this always happens — what makes you certain?" Isolates scope: "What's the smallest version that breaks?"

RubberDuck never gives the answer until you've exhausted the Socratic path. When you find the bug, it closes the session by naming the wrong assumption — so it doesn't come back.

Why $2? Because you don't need much from a rubber duck. You need the right questions. That's what this does.

The bugs you find yourself don't come back.