How to Remember What You Read | Reading System | Readwise, Instapaper, Memex
Based on Systematic Mastery's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Build a daily review loop that resurfaces highlights based on tags and feedback, so reading turns into repeatable recall.
Briefing
A practical “information digestion” workflow can turn scattered reading—books, articles, podcasts, even browser snippets—into daily, targeted recall. The core idea is to capture highlights and notes as they happen, then run a fast review loop that resurfaces the most relevant pieces at the right time, so insights don’t vanish after the reading session. At the center of that loop sits Readwise, which functions like a high-speed memory system for what matters to a person.
Readwise’s daily review pulls in configurable highlights (and sometimes question prompts) and asks the user to do nothing except revisit them—optionally tagging or adding notes. The payoff is mindset priming: revisiting meaningful passages can nudge how someone thinks before tackling the day’s work. The system can also be tuned by topic. For example, if someone is actively working on devops or Python, Readwise can be configured so the daily review prioritizes highlights tagged for those domains, making review time feel efficient rather than random.
The transcript highlights several mechanics that make the review loop usable. Tagging every highlight immediately increases later filtering and resurfacing precision. Readwise also supports feedback on how often a highlight should reappear, letting users keep “someday” ideas without discarding them. A “close deletion” feature hides specific words inside a highlight to force active recall, and the user notes a desired improvement: hiding multiple words at once. Another feature lets users turn passages into self-check questions—writing an answer now and revisiting the question later to see whether the meaning stuck.
Beyond review, Readwise helps expand the library. It recommends additional books based on existing highlights, and the user reports choosing several new reads through those recommendations. It also tracks streaks and performance, turning daily review into a game-like habit rather than a chore. Configuration screens show how tags can be weighted—programming, mathematics, domain-driven design, devops, cryptography—so the system continuously matches current priorities.
To feed Readwise, the workflow uses complementary tools. Instapaper acts as a “save first, read later” inbox for web articles: browser saves land in Instapaper, highlights and notes can be added there, and everything syncs back to Readwise. Memex differs by letting users highlight only a selected portion of what they’re viewing online—useful for short snippets like Slack messages or Stack Overflow questions—without importing entire pages. The transcript also mentions import sources for Readwise such as Kindle, Apple Books, Goodreads, Twitter, and podcast transcription via Air, plus a browser tool called Command for highlighting directly in the browser (though the user uninstalled it due to user-experience and privacy concerns).
Taken together, the system treats reading as raw material for recall: capture quickly, tag intentionally, review daily at speed, and route different content types through the tool that fits them best. That combination—fast resurfacing plus flexible capture—aims to make memory and understanding compound over time rather than reset after each session.
Cornell Notes
The workflow centers on Readwise as a daily review engine that turns saved highlights and notes into fast, targeted recall. Users revisit configurable highlights each day, often priming their mindset for current work (e.g., devops) by filtering what resurfaces via tags and feedback. Readwise supports active recall tools like hiding words in highlights and creating question-and-answer prompts to test retention later. To feed the system, Instapaper saves and highlights web articles for later syncing, while Memex lets users highlight only a selected part of online content (like Slack or Stack Overflow) without importing whole pages. The result is a “second brain” loop where reading becomes reusable knowledge through consistent, efficient review.
How does Readwise turn highlights into something closer to memory rather than a static archive?
Why does tagging every highlight matter in this system?
What does “feedback” do for highlights, and how is it used for long-term ideas?
How do Instapaper and Memex differ in how they capture content for later recall?
What role do question prompts and streaks play in sustaining the habit?
Why might someone choose to use multiple capture tools instead of relying on one?
Review Questions
- If Readwise is the review engine, what specific features make it support active recall (not just rereading)?
- How would you design a tagging and feedback strategy to keep daily reviews aligned with a shifting goal like “devops now, Python later”?
- Compare Instapaper and Memex: in what situations would you prefer highlighting a snippet over saving an entire article?
Key Points
- 1
Build a daily review loop that resurfaces highlights based on tags and feedback, so reading turns into repeatable recall.
- 2
Tag highlights immediately to make future filtering and resurfacing efficient, especially when priorities change.
- 3
Use Readwise’s active recall features (like close deletion) and question prompts to test understanding rather than passively reread.
- 4
Feed Readwise with the right capture tool per source: Instapaper for full web articles, Memex for selected snippets without importing whole pages.
- 5
Leverage recommendations and streak tracking to expand the reading list and sustain consistent review habits.
- 6
Treat “someday” ideas as scheduled resurfacing instead of discarding them, using Readwise feedback controls.