Chapter: --/4
Score: 00
Lives: 3 lives left
Best: --

Clean Code Rescue

Skip's code works, barely. Spot what makes it hard to read, then ship the tidy version that still does exactly the same thing.

Clean Code Rescue

Skip's Snack Club code works, but nobody can read it. Over four days, name what makes each short JavaScript snippet hard to read, then ship the rewrite that is clearer and still does exactly the same thing. One rewrite only looks tidier; another quietly changes the behaviour and turns the tests red.

12 snippets
Coding

How to play

Name the smell. Vague names, a magic number, copy-paste, too many jobs in one function or deep nesting. +5 when you get it.
Compare three rewrites. Flip through versions A, B and C. The code was never broken: you're making it readable.
Ship the clean one. +10 for the clean refactor. One version only looks tidier (+0); one changes what the code does: the tests go red and you lose one of 3 lives.
Four chapters. Names, copy-paste, the pyramid of ifs, then a feature freeze with smaller traps. Finish with lives left for +5 per heart.

Quick tips

The code already works. This isn't bug hunting. You're looking for what slows a reader down, not for a crash.
Names carry meaning. count and unitPrice beat a and b. A name like data, thing or NUMBER is still vague.
Name the reason, not the value. MIN_PASSWORD_LENGTH explains 12; TWELVE doesn't.
Copy conditions exactly. When you move or flip a condition, check every > and >=, and every !.
Guard order matters. With early returns, the first check that matches wins, so keep the special cases first.