All BlueprintsEducation

Flashcards with spaced repetition

A learner builds their own decks and reviews what they are about to forget rather than what they already know. How well a card went is what decides when it comes back, and the schedule is worked out from the answers rather than written down in advance.

L2–L4Level range
8Sprints
37Tasks
Backend and frontendBuilt as

What you’ll build.

By the last sprint

A flashcard app that decides when to show you a card again. Learners build decks and study only what is due today. Each answer pushes that card further out or brings it back sooner, and editing a deck keeps the history its cards already had.

What you’ll learn.

Each sprint is built around one skill. You show you have it in a pull request your team reviews, then explain it in a walkthrough.

Authentication

You can register and sign in a user, keep a request authenticated without asking for the password again, and explain where the credential lives in the browser and why there rather than somewhere else.

Search and filtering

You can search a list by keyword, combine that with filters, and say what the database does to answer the query — including which part uses an index and which part cannot.

Assessments that grade themselves

You can deliver an assessment, grade a submission, and show that answers cannot be read or resubmitted by the person taking it.

Tracking progress through material

You can mark a unit complete, compute overall progress, and keep it correct when the course itself changes.

Roles and permissions

You can give users different roles and have the server refuse what a role may not do — not merely hide the button — and show the refusal working against a request the interface never offered.

Going live

Somebody who has never met you can open a URL and use the product — and you can say what is different about the copy running there, where its secrets come from, and what you do when a release turns out to be wrong.

The roadmap. 8 sprints, 37 tasks.

Every sprint has a goal and a set of tasks. Open a sprint to see the tasks you will pick up.

Sprint 01

Whose cards these are

Somebody can make an account, come back to it a month later, and not be thrown out of the app while it is sitting open.

4 tasks
  1. A learner can register and land signed in
  2. Signing back in a month later still works
  3. A session left open over lunch does not throw anybody out
  4. Signing out on a borrowed machine actually signs you out
Sprint 02

Cards worth reviewing

A learner builds a deck of their own, and can still find one card in it when there are twenty thousand.

4 tasks
  1. A learner can make a deck and put a card in it
  2. Typing two hundred cards in one sitting
  3. A card can be corrected or thrown away
  4. Finding one card in a deck of twenty thousand
Sprint 03

The answer decides the date

How well a card went is what sets the next time it is seen, and the product is the one that works that out.

5 tasks
  1. A review session hands over one card at a time
  2. Each answer sets the next date, and the browser does not get a vote
  3. Getting a card wrong brings it back today without erasing its history
  4. Each answer says what it will cost before it is given
  5. A card that keeps catching somebody out is named as one
Sprint 04

What counts as today

What is due is decided against the learner's own day, and the number on the deck is the number of cards the session gives out.

5 tasks
  1. A learner says where they are and when their day starts
  2. Due is worked out when somebody asks, not written down in advance
  3. The clock on the device cannot make a card due
  4. The count on the deck is the number of cards the session gives out
  5. Crossing a time zone does not give anybody two Mondays
Sprint 05

Coming back to four hundred

Three weeks away is a queue somebody can finish in a sitting, not a wall they quit at.

5 tasks
  1. A day has a limit, and the learner sets it
  2. A capped day spends itself on the cards nearest to being lost
  3. A card recalled three weeks late is credited for surviving three weeks
  4. Cards a learner cannot face can be put aside
  5. The deck says what today holds and what is not coming today
Sprint 06

Studying off the schedule

A learner can practise anything at any time, and nothing outside a real review moves a date.

4 tasks
  1. Practice: any cards, any time, and no date moves
  2. What makes practice harmless is the product, not the screen
  3. Nobody can answer a card that is not theirs
  4. Practice does not pretend to be study
Sprint 07

The deck changed underneath

A deck edited today keeps the history its cards earned yesterday, and a card that now asks a different question starts again on purpose.

5 tasks
  1. Fixing a typo does not cost a card its schedule
  2. A card that now asks a different question can be started again
  3. Three hundred new cards in an old deck do not become a backlog
  4. A card moved to another deck takes its schedule with it
  5. Deleting a card does not rewrite what happened on the days it was answered
Sprint 08

Somewhere a phone can reach

The product is on the internet at its own address, usable one-handed, and a year of somebody's answers survives the machine it lives on.

5 tasks
  1. A stranger can open it at its own address
  2. Nothing it needs exists only on the laptop it was written on
  3. Five minutes at a bus stop, with one hand
  4. A release that turns out to be wrong is undone the same hour
  5. A year of answers survives the machine it lives on

Read before you build. The best engineers do.

Senior engineers read the docs before they touch the code. Every Blueprint comes with short documents on the product and its world, the kind a team hands a new hire. Read them well and you ask sharper questions and walk into every review prepared.

What you are building

The product, who it is for, and what finished means.

How forgetting works, and what a schedule does about it

The evidence behind spaced repetition, what an interval and an ease are, and why the schedule is computed rather than written down.

Build flashcards with spaced repetition.

Start your free week. Adaeze runs your kickoff, and Lars reviews every pull request.