Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Debrief

The debrief takes about 30 minutes. The course retrospective follows on the next page.

The chatter (10 minutes)

  • Show the worst decision trace of the afternoon. What did you change to eliminate it, where does that live in the types, and what did it cost on the latency target?
  • Which corner of the noise / false-alarm / latency triangle did you concede, and who at work should be making that call?

The test suite (15 minutes)

  • Each pair: count your suite by layer (example, property, statistical). What did the agent’s first suite look like by the same count?
  • Show the best property of the day. What bug does it catch that no example test could?
  • Your statistical verdicts: samples, threshold, confidence, and why those numbers. If you hit the flipping-verdict problem, what did it teach you about the difference between “we test it” and “we can make a claim about it”?

Closing question (5 minutes)

The acceptance table judged guardian in aggregate. The processes that judge your real systems work the same way, and increasingly so do the ones that judge LLM-produced code. What changes in your team’s definition of “tested” on Monday?