bugger.
A SMALL SPACE FOR BIG BREAKTHROUGHS

Good bugs.
Better instincts.

Practice fixing real Python and Rust bugs. Reproduce the failure, repair the cause, and prove your fix against regression tests. Build an instinct you can take back to your own code.

Explore without signing inNo setup. Just curiosity.
PyRsA little Python. A little Rust.
A whole new way to think.
LESS GUESSING. MORE “GOT IT.”
your next aha moment
BUG / 001 Easy

The cache that forgets.

A value is cached. So why is it being computed twice?

Py main.pySTARTER PREVIEW
01def resolve(records):02    memo = {}03    for record in records:04        key = record["key"]05        value = memo.get(key)06        if value is None:↳ hmm...07            calls += 108            memo[key] = record["value"]
×
Repeated nullExpected 1 lookup. The starter makes 2.
A clue, not a dead end
Read the report. Follow the evidence.

DELIBERATE PRACTICE.
REAL PROGRESS.

09handpicked challenges
02languages to explore
03levels of curiosity
∞room for the “aha”
01 / A DIFFERENT KIND OF PRACTICE

Less memorizing.
More figuring it out.

You learn a lot by making things.
You learn something different by fixing them.

Meet the bug.

Start with a real report, a small codebase, and a program that doesn’t quite behave.

READ. REPRODUCE. GET CURIOUS.

Follow the evidence.

Read the code, test your ideas, and connect the dots. A hint is there if you need it.

THINK. EXPERIMENT. TRY AGAIN.

Keep the understanding.

Ship the fix. Unpack the root cause. Take a better instinct into the code you write next.

FIX. REFLECT. MAKE IT STICK.
02 / THE BUG COLLECTION

Small challenges.
Lasting lightbulb moments.

Explore all 9 challenges
HANDPICKED. HUMAN-SIZED. WORTH YOUR TIME.

Real failure mechanisms. Original teaching code. A safe place to get it wrong.

BUILT FOR THE MOMENT IT CLICKS

No race to the answer.
Just a better way to get there.

No leaderboard. No ticking clock. Your saved progress, optional hints, and a little space to think. Because understanding beats a lucky guess.

A little more about Bugger
A FEW THINGS YOU MIGHT BE WONDERING

Curiosity
looks good on you.

Here’s a little more before you jump in.

What kind of challenges will I find?

Small Python and Rust programs with bugs adapted from documented open-source defects. Practice caching, cancellation races, request security, streaming parsers, text, time, and numeric bounds.

Do I need to install anything?

You can browse reports and starter code right away. Sign in to edit, save your drafts, and run code in the browser. Execution happens in an isolated remote environment.

Is this for beginners or experienced developers?

There are easy, medium, and hard challenges in each language. Each report lists its prerequisites, and optional hints help you get unstuck. Difficulty labels are provisional.

Is there a time limit?

No. Time estimates help you choose a challenge, but there is no ticking clock or leaderboard. Take the time to understand the cause, test a hypothesis, and learn from the explanation.

SOMETHING’S BROKEN. THAT’S A GOOD START.

Your next “aha”
is waiting.

Let’s find it