02 Anatomy of a review

What lands in your repository after every submission

A reviewer opens your branch, reads the diff line by line, and writes back a numbered list. Each entry quotes the exact line it refers to, carries one of three severity tags, and points at a direction to try.

The reviewer never commits a corrected version of your file. A solution you did not write is a solution you cannot defend in an interview, so the fix stays yours.

  • Line referenceFile path and line number, quoted verbatim, so you land on the code instead of searching for it.
  • Severity tagBlocker, should-fix or nit, so you know what has to change before the week closes.
  • Suggested directionA named pattern, a documentation link, or a question that reframes the problem.
  • No rewritten solutionThe second version is reviewed as closely as the first. Resubmission is required.
Read a real review thread

Review thread / anonymised

One hunk, three notes, one resubmission

Student 214, week six, third pass on the same file. Names are shortened. The code is copied from the thread without edits.

src/cart/checkout.jsv3 / 41 lines
 export function checkout(cart) {-  const total = cart.items.reduce((s, i) => s + i.price);+  const total = cart.items.reduce((s, i) => s + i.price * i.qty, 0);-  if (!total) return { ok: true };+  if (!Number.isFinite(total) || total <= 0) return { ok: false, reason: 'EMPTY_CART' };   return { ok: true, total }; }
Read the note taxonomy

Resubmitted 19 hours later. #1 closed, #2 closed, #3 kept open as a nit.

-  if (!total) return { ok: true };+  if (!Number.isFinite(total) || total <= 0) {+    return { ok: false, reason: 'empty-cart' };+  }   return { ok: true, total };
04 Reviewer capacity

Fourteen seats. Two reviewers. Seventy-two hours.

A cohort does not open until two reviewers are contracted. That one rule sets everything below: how many students we admit, how far a review queue can fall behind, and why resubmission is not optional.

  • Students per reviewer1 : 7
  • Review turnaround on written notes72 hours
  • Cohort cap14 students
  • Contracted reviewers before start2

A review submitted on Friday is answered by Monday. If a cohort fills before the reviewer pair is signed, the start date moves. The ratio does not. Line-referenced notes, a severity tag on every blocker, and a mandatory second version are the whole method.

See the next cohort date

04 / Resubmission loop

The second version is where the learning happens

Every project goes through two reviews, and the same reviewer stays on your thread both times. Version one comes back with numbered comments; version two is where you fix, defend or rewrite what was flagged. Resubmission is mandatory, and it is not a penalty. It is the part of the course where the code actually changes.

  1. Read each note against the file. Every comment carries a line range and a severity tag.
  2. Reply inline in the thread, then push the new commit to the same repository branch.
  3. The second review returns within 72 hours and references both versions side by side.

The cap does not change between passes: one reviewer per seven students. If a blocker is still open on the second read, you loop a third time with the same person. See how admissions schedules the loop.

Flat answers

Certificates, accreditation, job guarantees, cost

Four questions come up on every call. Here are the answers without the sales framing.

Cost details sit in the full cost table. If your question is not here, use the application form.

Admissions

One route in. Fourteen seats, seven students per reviewer.

Applying is a two-step conversation, not a checkout. Send the form, then sit a short code task so we can place you in the cohort your current level can survive. If your level does not fit, we say so and name the cohort that does.

  • Cohort size14 students
  • Review ratio1 reviewer / 7
  • Written review turnaround72 hours
Apply for the next cohort Read the full cost table