Back to the blog

Revising with AI, honestly: active recall, Feynman, quizzes

Method4 min read · 26 September 2026

The GetPack team

Using AI to revise is tempting: it can read your course material in seconds and hand you back a tidy summary. The problem is that reading a well-written summary creates a feeling of mastery that doesn’t hold up against a real exam question. It’s not cheating, just a method that doesn’t work very well: passively rereading a text is one of the least effective ways to make knowledge stick in memory.

What actually works, on the other hand, has been documented in cognitive science for a long time. Here are three well-established methods, and how an AI tool can help you apply them without ever doing the memorization work in your place.

Active recall: testing yourself beats rereading

The principle is simple to state and yet counterintuitive: it’s better to try to remember something, even if you get it wrong, than to reread it one more time. An educational resource from the Académie de Guadeloupe (a regional education authority) on cognitive-science-based practices sums it up this way: training regularly with tests improves long-term retention more than passively rereading your course notes.

In practice, this changes how you work through a chapter. Instead of rereading your notes a third time before an exam, you close the notebook and try to answer a question without any support, then check afterward. The same resource actually recommends rephrasing your course material as questions without the support material, then checking afterward, rather than simply rereading.

An AI can help here in a very concrete way: generating questions from your course material, asking them one at a time, and only giving the correction after your answer. That’s the difference between a tool that helps you test yourself, and a tool that just recites a summary you’ll passively reread.

The Feynman technique: explaining to check you’ve understood

The Feynman technique starts from a simple idea: if you can’t explain a concept in simple words, you haven’t really understood it yet, even if you think you know it. The principle is to explain the concept out loud or in writing, as if presenting it to someone who doesn’t know it, then spot where you get stuck, where you use jargon without defining it, or where your explanation is wrong.

This is exactly where AI can play a useful role, as long as it doesn’t do the work in your place. A good Feynman-technique skill should listen to you explain a concept in your own words, spot the gaps and undefined jargon, then ask you follow-up questions — rather than immediately giving you the full explanation. The goal isn’t to get a neat, ready-made explanation: it’s to discover, through your own successive attempts, what you don’t yet master.

Spacing: several short sessions beat one long one

The third principle concerns the timing of your revision rather than its content. According to researcher Shana Carpenter, cited on the reference site retrievalpractice.org, there’s no single, universal optimal spacing between two revision sessions: spacing is flexible, and that’s exactly what makes it a practical tool you can adapt to your schedule.

What is well established, though, is the comparison between cramming and spreading things out over time: cramming (reviewing everything at once, right before the exam) improves very short-term memorization, but the information is then forgotten quickly. Spreading the same amount of revision over several days or weeks, for an equivalent total time, noticeably improves long-term retention and your ability to reuse the knowledge in a different context. The general rule suggested is to let enough time pass between two revision sessions that the information is no longer fresh in memory — which can mean ten minutes or several days, depending on what you’re revising.

Translated into practical use: three hours of revision crammed in the night before an exam are worth noticeably less than the same three hours spread over six days, at half an hour a day.

What an AI should never do in your place

These three methods share one thing in common: they require that you be the one making the effort of retrieval, explanation, or answering. An AI that hands you the perfect sheet directly, the explanation already chewed over, or the answer before you’ve even tried to respond, short-circuits exactly the mechanism that makes these methods work. The useful role for an AI tool here isn’t to replace you, but to play the part of the examiner or the classmate you’re explaining things to: the one who asks the questions, spots the gaps, and sends you back to the effort — not the one who answers in your place.

One last habit to keep, whatever tool you use to revise: check your institution’s own AI usage rules, especially if certain exercises or assessments explicitly regulate its use.

Key takeaways

  • Testing yourself (active recall) reinforces long-term memorization better than simply rereading your course material.
  • The Feynman technique reveals gaps in understanding by forcing you to explain a concept in your own words.
  • There’s no universal optimal spacing, but spreading revision over several days is noticeably more effective than cramming, for an equivalent total time.
  • A useful AI revision tool asks questions and waits for your answer; it should never give the correction or explanation before you’ve tried.
  • Always check your institution’s AI usage rules before relying on one for graded work.

This principle of prompting you further without giving the answer right away is exactly what the methode-feynman skill applies.

Sources

  1. The most common question I get asked about retrieval practice (and the answer) — retrievalpractice.org (Dr. Shana Carpenter) · accessed 26 September 2026
  2. Pratiques pédagogiques basées sur les sciences cognitives pour améliorer la mémorisation — Académie de Guadeloupe · accessed 26 September 2026

Read the next article

Career26 September 2026

Choosing your apprenticeship with real employment data

Code27 September 2026

Learning to code in the age of AI: what you still need to know how to do yourself

Code27 September 2026

The one-page spec to write before you prompt an AI to code

Thesis27 September 2026

How to cite ChatGPT or Claude in a thesis: APA, MLA, ISO 690

Code27 September 2026

Claude Code for beginners: install, first launch, CLAUDE.md

AI news27 September 2026

Claude Opus 5.5: what really changes (and how to use it to study)

Analysis27 September 2026

The AI race: why some people are scared and others aren't

Code27 September 2026

Building your first MCP server, step by step

Code27 September 2026

Deploying your first site for free: Vercel, Netlify, Cloudflare Pages, or GitHub Pages

Explainer27 September 2026

AI detectors: are Turnitin, GPTZero and Compilatio reliable?

Code27 September 2026

Writing your own Claude skill: structure, SKILL.md, and a description that triggers

Career27 September 2026

France's national student-entrepreneur status (SNEE) and the PEPITE network, explained

Analysis27 September 2026

France in the AI race: Mistral, energy and talent

AI news27 September 2026

French Tech and AI: the French startups to know in 2026

Code27 September 2026

Git without fear: commit, branch, remote explained, then the commands that save you

Explainer27 September 2026

Chinese AI: DeepSeek, Qwen, Kimi… why Europe is wary

Health27 September 2026

AI in medical school: study for PASS, LAS and the EDN safely

Tools27 September 2026

Free AI for students: every offer and discount (2026)

Career27 September 2026

AI on an internship or apprenticeship: what’s allowed, what isn’t

Code27 September 2026

From IDE to ADE: coding with AI agents in 2026

Code27 September 2026

Reading an error without panicking: the anatomy of a stack trace (Python and JavaScript)

Tools27 September 2026

Best AI for students in 2026: the honest comparison

Tools27 September 2026

New AI models in 2026: which one should you study with?

Tools27 September 2026

French AI tools you’ve never heard of: Noota, Moshi, Vibe…

Analysis27 September 2026

Why AI is so expensive (and American AI even more so)

Code27 September 2026

How to prompt an AI coding tool well: the method that changes everything

Code27 September 2026

Securing a vibe-coded app: 7 mistakes to fix before you publish

Code27 September 2026

Slopsquatting: when AI recommends packages that don't exist

Weekly brief27 September 2026

AI news roundup: the week of September 21–27, 2026

Code27 September 2026

Vibe coding: what it actually means (and how not to mess it up)

AI news27 September 2026

Why Yann LeCun wants AMI: AI beyond LLMs

Tutorial26 September 2026

Connect an MCP connector to Claude without writing a line of code

Degrees26 September 2026

Choosing your program with real MonMaster and InserSup data

Method26 September 2026

APA 7, ISO 690, Vancouver: how to cite your sources properly

Explainer26 September 2026

ChatGPT's 'hidden codes' on TikTok: fact vs. fiction

Health26 September 2026

Medicine: revise for the EDN with France's public drug database

Career26 September 2026

Internship pay and apprentice wages in 2026: the rules

Explainer26 September 2026

AI and academic integrity: what universities actually say

Tutorial26 September 2026

Installing a skill in Claude in 2 minutes

Thesis26 September 2026

Thesis: building your research question and outline with AI

Method26 September 2026

Building your exam study schedule with AI, the right way

Join GetPack

Already have an account? Sign in