Project A: canscan
Including a 10 minute break, this session should take about 3 hours and 30 minutes. It contains:
| Segment | Duration |
|---|---|
| Brief | 10 minutes |
| Project work, part one | 1 hour 15 minutes |
| Break | 10 minutes |
| Project work, part two | 1 hour 15 minutes |
| Debrief | 40 minutes |
Your first project with the agent. It’s a command-line tool that reads CAN bus log files and answers questions about them, small enough to finish in an afternoon and realistic enough that everything from this morning shows up in it.
This project practices:
- Crate evaluation. The spec names no crates. Your agent will propose some, and deciding whether to accept them is your job.
- Judging toolchain suggestions.
clippyandrustcwill make suggestions. Some are right for this tool and some aren’t. The agent tends to accept all of them. - Spec iteration. The spec is incomplete, like most specs. When reality disagrees with it, amend it in writing and regenerate.
- The morning’s material: skeleton first, then smell triage on the output.
Working agreement: pairs. The less experienced Rust reader drives the
agent, the more experienced one reviews out loud. Swap at the midpoint. Record
findings in REVIEW-LOG.md as smell, principle, and prompt. The log is an
input to the debrief.