Learn to read the evidence.
Writing code and debugging code are different skills. Bugger gives you small, broken programs adapted from real GitHub issues, so you can practice the part that usually happens after the tutorial ends.
Understand the report
Read what went wrong, the expected behavior, and the reproduction. Python and Rust challenges each have easy, medium, and hard levels.
Reproduce and investigate
Sign in with GitHub or an email code. Run the broken program, inspect its output, and edit the code in the browser. Your draft is saved to your account.
Test your hypothesis
Run checks the visible examples. Submit checks those examples and additional regressions against the same documented contract. Each result belongs to the exact snapshot you sent.
Connect the dots
After an accepted submission, read the root cause, the adaptation’s simplifications, and the original GitHub issue. Try to explain why your correction works.
Depth without the setup
These are original teaching adaptations, not full reproductions of upstream projects. Each exercise keeps the failure mechanism and explains what changed. Difficulty labels are provisional; estimated time is guidance, not a limit.
Your work is yours
Public reports contain no learner submissions. Saved drafts and results are private to your account. If two devices edit the same draft, Bugger asks you to resolve the conflict.
Explore the collection →