A DAILY BUG HUNT FOR DEVELOPERS
Three broken code snippets a day. Read what should happen, see what goes wrong, tap the guilty line.
Free. Log in with Google.
3 new bugs every day. About 3 minutes.
HOW POINTS WORK
ABOUT
More and more code is written by tools. The skill that matters most is being able to read code and notice what is wrong with it. BugTap is a small daily game to practise exactly that.
Every bug is a short, realistic snippet with one clear mistake. After you answer, you get a plain explanation of what is wrong, why it happens, and the fix, so you learn something even when you miss.
HOW EVERY BUG IS MADE
Written around a real pattern.
The kind of mistake developers actually ship.
Checked by a test.
The test fails with the bug and passes with the fix.
Reviewed by a person.
Nothing goes live without a human reading it.
TOPICS
Every bug is tagged with a topic and a concept, so you know what you are practising. You see each bug once, then you can study the ones you missed.
YOU WILL PRACTISE
YOU WILL PRACTISE
MORE EVERY WEEK
Easy, medium and hard bugs for JavaScript and React, with new ones added all the time.
HOW TO PLAY
Read the clue.
One line for what should happen, one for what actually happens.
Tap the guilty line.
You can change your mind until you lock in.
Lock in.
The closer you are, the more points you earn. 300 is the most per round.
Learn why.
What's wrong, why it happens, and the fix, in plain words.
Five hearts, one lost per miss. Hearts are just for fun, so you always see every explanation.
React Updating state
You click Add, but the screen never changes.
The bug is on lines 5 and 6You picked line 7
BugTap #12 (React) 🟩🟨🟩🟥🟩 385/500 in 1:12
BUG PATTERNS
The bugs that show up again and again. Log in to read the full write-ups.
REACT
onClick={fn()} runs right away
Why a button can fire before anyone clicks it.
REACT
Changing state without changing it
Why push() and setState with the same array does nothing.
REACT
Why key={index} breaks lists
How React uses keys, and what goes wrong with positions.
REACT
Stale closures: the timer that sticks at 1
Why a function inside useEffect keeps an old value.
REACT
The effect that never stops running
Why an object in the dependency list causes an infinite loop.