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 40 minutes. Have your review log open.

Each pair presents (20 minutes)

Each pair gets three minutes:

  1. One smell you caught: show the code, name the principle, read the prompt that fixed it. Did the fix work?
  2. One thing you kept: a construct that looked like a smell and survived review with a written justification.
  3. Your spec amendment: what did you add when reality disagreed with the spec?

Themes (15 minutes)

  • The dependency trees. One task, several trees. What selection criteria did the group converge on for accepting an agent’s crate proposal?
  • Clippy. Where was a suggestion right, and where was following it wrong? What should the team’s policy be: who may write #[allow], and what must accompany it?
  • Reality versus the starting spec. What is the difference between the spec you were handed and the spec you finished with, and who on your real team owns that difference?

Close (5 minutes)

One sentence per pair: what will you put in the skeleton next time that you put in a review comment today?