How it works
Clone it, fix it, ship it.
10xDebuggable is not a puzzle site with a submit box. It is a backlog of real tickets inside working codebases, reviewed the way a colleague would review them. Every ticket you close is one rep.
- 01
Pick a ticket
Browse projects by stack and difficulty. Every ticket carries the business context, the observed symptoms, and the acceptance criteria — the same things a real ticket carries.
- 02
Download the whole project
Fork the repo (or download the zip to read it), run it locally with the project's setup steps, and reproduce the problem before you change anything. Reproducing it is half the exercise.
- 03
Fix it on a branch
Every ticket names the branch to work on — fix/… for bugs, feat/… for enhancements. Meet the acceptance criteria, add the test, keep the diff reviewable, then push the branch.
- 04
Submit and get reviewed
Paste your fork URL, the branch you pushed, and a short write-up of the root cause. A human reads it and replies with real feedback, usually within a day.
Levels
Four rungs in every project
Start where you're comfortable and climb. The rungs mirror how responsibility actually grows on a team.
Questions
Reasonable objections
Is there a browser IDE or an online runner?
No — deliberately. You work locally, in the environment you actually use. That is closer to the job and it keeps the platform focused on the thing that matters: the quality of the tickets.
How is my submission judged?
By a person reading your diff against the acceptance criteria. Passing tests is the floor; what gets you approved is a correct root-cause fix that a reviewer would merge.
Can I resubmit after a rejection?
Yes. Rejections and change requests come with feedback, and you can submit again as many times as you like. A ticket counts once toward your points.
What does it cost?
Nothing during early access.