Skip to main content

Evidence-based review and repair

This required 20–28-hour package replaces the former 2–3-hour guided lookup lab. Allocate 5–7 hours to lessons and predictions, 8–12 to review and repair, and 7–9 to decision evidence, assessment and delayed transfer. The semester workload ledger includes it once within Module 5.

Learning sequence​

  1. Contract-led review.
  2. Regression evidence.
  3. Decision records and handoff.
  4. Trace practice, runnable lab, then AR1–AR6 assessment.

You review deliberately flawed code, demonstrate defects, repair it and justify the final verdict. Reuse the evidence in the semester project; no additional application is required. Existing discovery, usability and accessibility work remains required and is budgeted separately.

Sources and boundaries​

Use Google's review standard, its review checklist, and Nygard's ADR essay selectively. Primary pages checked on 2026-10-23. Existing book references support concepts; no purchases or book conversion are needed. Teaching examples are original.

The lab is a synchronous, read-only, in-memory lookup over trusted fictional rows. It assumes an already-authorized tenant context. Passing its checks does not establish real authentication, database isolation, safe concurrent updates or production security. Independent subject review and learner timing pilots remain pending.