Running the Simulation

Treat this module's problems as a mini-contest: choose your own order, allocate ~35 minutes each, and write down your decisions as you make them. Afterward, fill the review:

1. What did I solve, and at what time?
2. Where did the pipeline stall, and at which stage?
3. Which observation unlocked it — and how long until I found it?
4. Did I prove it, or trust it?
5. What would I attack first on my own accepted solution?

Reading your own review

• Stalls at model → vocabulary problem: re-read Module 3's reformulation patterns.
• Stalls at observe → experiment more, theorize less: your tables were too small or too unstructured.
• Stalls at implement → the complexity family was chosen before the observation was proven; you rewrote the code.
• Overruns at attack → the checklist was skipped; the fix is mechanical, not intellectual.

The meta-point

Simulations are not for verifying that you know things. They are for exposing the sequence you actually run under pressure — which is almost never the sequence you believe you run. The gap between the two is the last skill this course can give you.