Greg Yung Logo

Bug Hunt 🐛

Every codebase has bugs. Find them before production does.

Why is this here? No reason at all! I was thinking back on the games of my childhood, and Minesweeper came to mind. I love how simple it is: a grid, some numbers, and math a fourth grader could do. Yet it's still tricky enough to eat a whole afternoon while you chase your own personal record.

So I wondered what a spin-off would look like from an engineer's point of view. The answer was obvious: finding the bugs. Every square is a line of code. Every number is a teammate saying “something nearby looks off.” Every bug you miss ships straight to production, usually on a Friday afternoon.

The irony isn't lost on me: I wrote a game about finding bugs, which means this game almost certainly has bugs. If you find one, congratulations, you're a natural. File a ticket and I'll add it to the backlog. Right behind all the others.

Bugs left: 10
Time: 0
Best Beginner time: —
beginner.ts

Open any line to start the review. Right-click or long-press to tag a suspected bug.

How to play

  • Open a line by clicking or tapping it. Your first one is always clean.
  • A number tells you how many bugs are hiding in the eight squares around it. A blank square has none, so its neighbors open automatically.
  • Tag a suspected bug with a right-click. On a phone, long-press, or switch the toggle under the board to Tag. Tags are just notes to yourself; you win by opening every clean line.
  • Shortcut: click a number that already has that many tags around it to open the rest of its neighbors at once. Tag carefully: one wrong tag and a bug ships.
  • Keyboard: Tab into the board, move with the arrow keys, press Enter or Space to open and F to tag.