Bottleneck autopsies

Bottleneck autopsies. The four phases fail differently:

• Reading overrun: you re-read the spec three times → underline the operator-deciding words in one pass (module 13's circles). Re-reading without marking is a loop, not reading.
• Planning overrun: you code before knowing the shape → the five-second classification and one-line restatement (module 17) are the cure. Planning is two sentences, not a paragraph.
• Coding overrun: you know the plan but the syntax drags → pattern fluency drills (modules 5–10). This is the only bottleneck fixed by typing more.
• Testing overrun: you submit unverified and churn on failures → run the boundary cases FIRST (empty, single, ends), because that is where your own bugs live.

A mismatch between your diagnosis and the log is itself information: most students misdiagnose "coding" for "reading."