Bugdle is a daily code-review puzzle. Every day you get a small chunk of plausible production code with one intentional bug. You have six attempts to identify the language, click the buggy line, and write the replacement that fixes it.

Instead of pattern matching letters, you're pattern matching the kinds of mistakes that ship to production every day: SQL injection, off-by-one errors, race conditions, stale state, leaked file handles, broken authorization checks. Each puzzle is an original snippet — not a sample lifted from an existing codebase — written specifically to capture one named bug class.

Who runs Bugdle?

Bugdle is independently operated as a personal project by an engineer who has spent enough years in code review to think the world needed a five-minute daily warm-up for the muscle. The site is not affiliated with, endorsed by, or sponsored by any other puzzle publisher. For business inquiries, puzzle pitches, or anything else, see the contact page.

Why does it exist?

Code review is a craft. It rewards a specific muscle: the instinct that something is off before you can articulate why. That muscle gets stronger with reps. Most engineers do reviews under deadline pressure, which is exactly when intuition is most valuable and most fragile. A daily five-minute drill, with no stakes, is a great way to keep it sharp.

Each puzzle is also designed to teach. The postmortem after every game explains why the bug is dangerous, where it tends to crop up in real codebases, and the heuristic that would have caught it. The category and language hub pages collect related puzzles and give you a place to read about a whole class of bug.

How content is written

Every puzzle, every postmortem, and every hub-page article on Bugdle is written by the operator. We use authoring tools the way an engineer uses an IDE — for spell-check, for fact-checking against canonical references like CWE and the relevant language specs, and for catching the second-pass typos that always slip through. The voice, the structure, the choice of which heuristic to spotlight, and every line of the code snippets are human-authored. We don't ship machine-generated bug descriptions; the puzzles would not be useful to read if we did.

How it's built

Bugdle is a static, edge-deployed Next.js app. There's no backend. Your streak lives in your browser's local storage. The puzzle catalog is a static module — every snippet is hand-curated and tested against its own canonical fix.

Browse

Contact

Questions, puzzle pitches, bug reports, advertising or partnership inquiries, privacy questions, or DMCA notices — the contact page has the right address for each. The general inbox is hello@bugdle.dev.