Agenda

  1. Warm-up: Name That Error — drawn from the wreckage of yesterday
  2. Discussion: Mistakes Are Data — your client’s confusion is the most valuable thing you collected this week
  3. Tool: Using the Debugger, on a bug you cannot find by reading
  4. Build period two: fix what the real user broke, then stop adding things. Stopping is a skill, and it is assessed.
  5. Log it in your Code Journal

Things to do before our next class

  • Milestone: every bug from the client test either fixed or written down, honestly, as a known limit.