# Lab Debrief and Collaborative Debugging

Beginning with Lab 2, each lab cycle starts with a 10-minute discussion of
the previous lab. The purpose is to make debugging and scientific decision
making visible to the whole class.

Lab 2 spans two weeks, so its second week opens with a short check-in on
Part A instead of a full debrief. No debrief card is due in the middle of a
lab; the Lab 2 card is due before Lab 4 begins.

Before class, complete the debrief card at the end of your previous notebook.
Bring one of these:

- a problem you solved, including the evidence that led to the fix;
- a problem you have not solved, including what you already tried;
- a design choice or verification check if you did not encounter an important
  problem.

An unresolved problem is a useful contribution. Do not hide it or replace it
with a vague statement such as "the code did not work." Include the error
message, unexpected value, figure, or small example that shows what happened.

## The 10-Minute Routine

1. **0-5 minutes:** Students compare debrief cards in small groups and
   work one unresolved problem together.
2. **5-10 minutes:** Two to four students or groups report to the class,
   and the class records one reusable lesson.

## A Useful Problem Report

Use this sequence:

1. What were you trying to calculate or show?
2. What did you expect?
3. What actually happened?
4. What evidence did you collect?
5. What did you try?
6. What fixed it, or what should the class test next?

Students take turns presenting across the semester. Participation is based on
preparation, evidence, listening, and useful help. It does not depend on
arriving with a solved problem.