Course Close and Retrospective

The retrospective takes about 15 minutes. Before people scatter, collect everything the two days produced into one repository.

Artifacts produced

• Smell Catalog v1: the merged table from Day 1, plus what the review logs added over the two days.
• The skeleton standard: Project B’s closing list of types, error conventions, and doc-contract habits every new crate should start from. A cargo generate template is the natural next step.
• The testing ladder: example, property, statistical, with Project C’s layer counts as the baseline and the sample-size question as an open item.
• A working definition of review: smell, principle, prompt, with the rule that a recurring prompt gets promoted into the skeleton.

The three skills, restated

1. Specify architecture in types and signatures, by hand. Bodies are generated; skeletons are written. The skeleton is the spec, and the compiler enforces it.
2. Recognize design problems quickly. Triage by signatures, types, and smells before bodies. A mix of conventions is a finding on its own.
3. Turn findings into prompts, and turn recurring prompts into skeleton changes.

Retrospective (one sentence per person, three rounds)

• Something that clicked.
• A sticking point you hit and will now recognize.
• One practice you’ll introduce in the team’s real workflow this month, stated concretely enough that a colleague could check.