Debug the signal.
Ship the fix.
Production-shaped debugging labs across APIs, config, concurrency, and infrastructure. Reproduce the failure, follow the evidence, and prove the smallest safe change.
Cache stampede without coalescing
Concurrent cold-cache callers each kick off their own expensive compute, overwhelming the worker.
Choose a failure mode.
Search by symptom, then filter by source, status, or difficulty. The featured lab is highlighted at the top so you always have a strong place to start.
No labs match that combination.
Try a broader source, a different difficulty, or clear the search.
tip · press / to refocus search
What are developers debugging?
Questions, dead ends, and useful investigation clues from real public Practice threads.
What developers are doing.
Recent public activity from developers who chose to share their Practice work.
More ways to practice.
Move from a focused drill to open-source history or company-style patterns when you want a different kind of debugging pressure.
Focused exercises
Train code review, system tracing, CI diagnosis, incident response, and fast debugging instincts.
Explore pathOpen-source labs
Practice against safely recreated public bug-fix history from the libraries that actually broke.
Explore pathCompany-style prep
Train backend and infrastructure failure patterns without affiliation claims.
Explore path