One hidden bug. Click the line you suspect. See your time and where the community guessed. Every bug comes with a full write-up: the rule it breaks and the fix.
# Build the leaderboard: each team's average score, in whole points.
scores = {"red": [2, 3], "blue": [3, 4], "green": [4, 5]}board = {}for team, pts in scores.items():
avg = sum(pts) / len(pts)
board[team] = round(avg)
ranked = dict(sorted(board.items(), key=lambda kv: -kv[1]))
print(ranked)
# expected: {'green': 5, 'blue': 4, 'red': 3}# actual: {'blue': 4, 'green': 4, 'red': 2} (!)Every bug on this site gets a full article: the exact language semantics, why it bites in real code, and the fix.
Paste your own code, mark the bug, and get one script tag that drops the puzzle into your post or docs. Readers solve it inline; the share card brings them back.
<script> tag into your post.<script src="https://onebug.dev/embed.js" data-puzzle-id="your-id" data-theme="auto" async></script>
Carries "Powered by OneBug" and links readers back to your puzzle.
I read code review like other people read crosswords. So I built one bug, one shot, and shipped it in public - no funding, no roadmap deck, just a puzzle a week and the numbers behind it.
- Robert · @rsz_me · building OneBug in public.