One page-turn, replayed

← Back to the case study

This is the loop I use instead of taking notes, walked through one page at a time. Click the button and follow it down.

The steps and the mechanism are real. The course material is not mine — I swapped in a page about HTTP caching so nothing about what I'm actually studying is published here. If you write software you may well get the quiz at the end wrong, which is rather the point.

watcher idle · waiting for a page change
The course page

Nothing yet. Click “Turn the page”.

What I got back

Nothing yet.

I click Next in the course. I don’t paste anything, and I don’t tell it I moved.
ASK IT ANYTHING · WHILE THE PAGE IS STILL OPEN
Ask at least one thing first.
BANKED · q-047 · CH. 2 · CACHINGtrap

Written from the passage above, while the passage was still on screen. It carries the explanation it came from, which is the receipt that nothing was invented.

flagged trap — tests a commonly-confused pair, so review weights it heavier

It doesn’t quiz me now, while I’d just be parroting it back.
REVIEW · DUE TODAY · MIXED WITH OLDER CHAPTERStrap

A response carries Cache-Control: no-cache. What is a cache allowed to do with it?

    That’s the loop. Read the page, get it back in plainer words, ask whatever didn’t land, bank a question from the passage, and get tested on it once you’ve started to forget. Anything you got wrong is logged by cause, so the next quiz knows what to contain.

    The quizzes themselves are one self-contained HTML file, generated from the bank by a 159-line Node script with no dependencies. Here’s a full one, or read the case study.