Module 2 · Daily workflows
Reviewers who probe real data, not the summary
In short
A good review does not read the implementer's report and agree. A separate reviewer compares the diff with the plan and probes the code against a masked data copy, including empty values. Findings are written as repeatable evidence.
After this lesson you can
- Assign a reviewer separate from the implementer and give them the plan, diff and verification commands, not the implementer's summary
- Probe query and filter changes against a pseudonymised data copy, including empty values and odd shapes
- Write review findings as repeatable evidence: command, input, expected result and actual result
Sign in to read this lesson
The title and summary are open to everyone. The full lesson is for signed-in learners.