A typical bootcamp review happens in three places: a live call that vanishes, a Slack thread that scrolls away, and a GitHub comment buried under the next commit. Six weeks later the student makes the same architectural mistake because nothing about the feedback attached itself to the code they wrote. Annotated PDF review changes the medium: the exported code listing becomes the canvas, and every note sits permanently beside the exact line it discusses.
The review workflow that sticks #
- Export the submission to PDF — the exercise, the code, and the spec in one document
- Highlight the defect, annotate with the rule it violates and one reference example
- Ask one Socratic question per finding so the student fixes it themselves
- Student re-submits with responses written against your annotations — the dialogue lives on the document
Because annotations are anchored, they become revision material. Before the assessment, students re-read their own reviewed PDFs — the complete history of their mistakes and corrections — which is a far more personal study guide than any generic checklist. Instructors benefit symmetrically: recurring annotation patterns across a cohort reveal exactly which lesson needs to be retaught.
Pair it with the bootcamp rhythm #
Weekend project submissions reviewed as annotated PDFs, weekday standups live, and peer reviews where students annotate each other's exports using the same convention. The shared annotation grammar — defect, rule, question — teaches code review as a transferable professional skill, which is precisely what employers interview for.