Review System

Transform passive note-taking into active learning through spaced repetition.

Why Review?

The problem with traditional notes: You write them, they sit in a folder, you never look at them again. Even if you do revisit them, passive re-reading creates an illusion of knowledge—it feels like you know something, but you can't actually recall or apply it when needed.

The science: Research shows that:

• Active recall (testing yourself) is far more effective than passive review
• Spaced repetition (reviewing at increasing intervals) optimizes long-term retention
• Immediate feedback helps correct misconceptions and deepen understanding

How Flint helps:

1. Mark notes for review
2. AI generates contextual challenges testing your understanding
3. You respond from memory (active recall)
4. AI provides feedback on your response
5. Schedule next review based on performance (spaced repetition)

Quick Start

Enable review on a note:

• Click the "Review" button on any note
• Or ask the AI: "Enable review for this note"

Review your notes:

• Click "Review" in the sidebar when you have notes due
• Answer the AI-generated challenge
• Rate your confidence to schedule the next review

That's it. The interface guides you through the rest.

What to Review (and What to Skip)

Review notes that:

• Contain core concepts you need to internalize
• Explain technical knowledge (APIs, architectures, patterns, algorithms)
• Document important decisions and their rationale
• Capture learning from courses, books, or research papers
• Describe processes you need to remember but don't use daily

Don't review notes that:

• Are pure reference material (just search when needed)
• You naturally revisit often in your work
• Are temporary or time-sensitive
• Contain trivial information

Quality over quantity: Better to have 20 well-chosen notes reviewed consistently than 100 notes sitting neglected in your queue. Start small, add more as your practice solidifies.

How to Make Reviews Effective

Respond Thoughtfully

When the AI challenges you, resist the urge to peek at the note. The discomfort of trying to recall is what builds understanding.

Good response:

REST principles include:
1. Client-Server: Separation of concerns between UI and data
2. Stateless: Each request is self-contained
3. Cacheable: Responses explicitly indicate cacheability
...

The main benefit is scalability—stateless servers can
handle requests independently.

Poor response:

I know this

Use your own words. Explain connections. Show understanding, not just memorization.

The goal isn't to review everything you write. It's to internalize the specific concepts that matter for your work and thinking. Start small, be consistent, stay honest about what you know and don't know. The system works if you use it—but only if you don't let it become a burden.