Context and introduction guide for giving scholars rubber ducks as debugging tools (around Day 3-4). Reference this when you're ready to introduce rubber duck debugging as a fun, memorable moment that teaches scholars self-sufficiency! This resource and the associated supplies are for In-Person Camps only.
What is Rubber Duck Debugging?
Rubber duck debugging is the practice of speaking your code out loud to an inanimate object (like a rubber duck). By translating code logic into spoken language, programmers are forced to engage different parts of their brain, often catching their own mistakes in the process!
Why it Works:
- Line-by-Line Logic: It encourages scholars to slow down and verify what the code actually says, rather than what they think it says.
- Self-Sufficiency: It provides a "first line of defense" before asking an Instructor or IA, empowering scholars to be independent problem solvers.
- Language Processing: Moving from "reading" to "speaking" helps identify gaps in logic that are easily missed when scanning a screen.
The "Big Reveal" Activity Ideas
In-person camps receive rubber ducks as part of their camp supplies. While there is no prescribed time to introduce them, we recommend a "Big Reveal" around Day 3 or 4, just as scholars begin diving into challenging independent work.
This timing is intentional: it transforms a functional tool into a high-energy community milestone at the exact moment scholars need it most. Use the ideas below as inspiration to find an approach that fits your camp's unique energy!
Idea 1: The Desk Surprise
Create a "magical" moment where the ducks appear while scholars are away from their computers.
- What to do: Coordinate with your IAs to take scholars to a different space (or outside) for a 10-minute brain break. While they are gone, place a duck on every scholar's keyboard or workspace.
- The Reveal: When scholars return to the surprise, take a moment to explain the history and purpose of their new coding companion.
Idea 2: The Great Duck Hunt
Turn the distribution into a community-building scavenger hunt.
- What to do: Hide the ducks in various (safe) places around the room. Give each scholar a clue or a "mission" to find their specific duck.
- The Reveal: Once everyone has found their partner, share the purpose of rubber duck debugging and how this new companion can help them on their coding journey.
Example Script:
“Congratulations! You all have been working so hard learning SQL, and we’ve been so impressed by how you’re tackling bugs. To support your journey as developers, we have a special professional tool for you… IT’S RUBBER DUCKS! In the industry, we use this friendly inanimate object for 'Rubber Duck Debugging.' Let's talk about how to use your new coding partners.”
Building Camp Culture: Ongoing Engagement
Once the ducks have been introduced, use these ideas to keep the momentum going and integrate the ducks into the camp community.
- Duck Naming Ceremony: Give scholars 2 minutes to name their ducks and introduce them to their neighbors.
- Social Content: Encourage scholars to include their ducks in project photos or "day in the life" snaps for camp memories.
- "Dress Like Your Duck" Theme Day: Announce a theme day where everyone (including staff!) wears colors to match their rubber duck!
The History
In the book The Pragmatic Programmer, a story is told of a developer who would carry a rubber duck and explain their code line-by-line to it. This forced the programmer to scrutinize every detail of their logic. Today, it is a staple of developer culture and a reminder that even the best experts need to "talk it out!"
Best Practices
Normalize the "Talk" | Some scholars may feel silly talking to a toy. Lead by example—when a scholar asks you for help, ask them: "Have you explained this line to your duck yet? I'll listen while you tell them what this function is supposed to do."
Use it for Content Review | If a specific concept (like Loops) is tricky, have scholars explain how a loop works to their duck in pairs during Opening Circle.
Focus on the Logic, Not the Bug | Remind scholars that the goal isn't to "find the error" but to "explain the story of the code." The error usually reveals itself during the story.
Rubber Duck Checklist
Ensure you have enough ducks for every scholar
Plan your “big reveal” moment
Decide how to incorporate your ducks into the camp culture
Take photos of the ducks "helping" scholars code!