0
Challenge · 49Interview Gauntlet
Debugging gauntlet
Debuggingused in ~88% of apps
Almost every Next.js 16 bug an interviewer hands you is one of four shapes: a hydration mismatch, stale cache, a 'use client' violation, or a page that silently went fully dynamic. The person who can name the shape on sight — before reading the stack trace — is the one who looks senior. This concept drills the on-sight diagnosis.
Core idea. Most App Router production bugs collapse into four recurring failure shapes. A senior debugs by pattern-matching the symptom to a shape first (Was the HTML different on the client? Is the data older than my write? Did a server-only API run in a client file? Did a request-time input pull rendering out of the static shell?), then confirms with one targeted check — instead of reading the whole stack trace top to bottom.
poke it, drag it,
try to break it
try to break it
no slides here.
you drive.
you drive.
Playground, this isn't a screenshot
bug 1 / 5 stale closure
Interval always logs 0
useEffect(() => {
const id = setInterval(() => {
console.log(count); // always 0
setCount(count + 1); // stuck at 1
}, 1000);
return () => clearInterval(id);
}, []); // empty depsbroken behavior
press Run to watch the symptom
Predict the broken behavior first, then Run to confirm, then Reveal the one-line fix. Cycle all 5 classics.
↑ play a little first, then dig in