Notes That Don't Just Sit There
How Fennie's notes spawn quizzes and flashcard decks in two clicks — and end up in tomorrow's plan instead of a folder you never open.
Notes That Don't Just Sit There
Here's the dirty secret about note-taking: most students are doing it wrong. Not in the "you should use the Cornell method" sense. In the "you'll never open this document again" sense.
Pull up your laptop. Look at your Notes folder from last semester. How many of those files have you opened in the last 30 days? For most people, the answer is zero. Maybe one, the night before a final, when you skimmed it and felt nothing stick.
Notes that sit in a folder are basically a journal. Useful for nostalgia. Not useful for learning.
The job of a note is to come back. To get tested. To get spaced and repeated until the thing inside it actually lives in your head.
That's the whole reason notes work the way they do inside Fennie.
The pivot: notes are an input, not a product
Fennie has eight things that talk to each other: Course, Calendar, Plan, Task, Note, Quiz, Flashcard, and Memory. Notes aren't the destination. They're the raw material that everything else feeds on.
Take any note. Click "generate quiz." You get a quiz pulled directly from what you wrote, three difficulties, your choice of question types. Click "generate flashcards." You get a deck.
Two clicks. That's the whole pivot. Your messy lecture notes from Tuesday become Wednesday's quiz, which becomes the spaced-repetition deck that shows up in your plan for the next two weeks.
The note doesn't sit. It works.
A real evening
Let me walk through what this actually looks like for a real person. Call her Maya. Sophomore. Pre-med. Tuesday is orgo lecture, 9:30am.
9:30am. She's typing into Fennie's note editor while Dr. Hannan paces. Markdown, because it's faster than fighting with Word formatting in real time. Headings for the major topics, bullets for the substeps, dollar signs around mechanism arrows because LaTeX renders cleanly in the preview.
The note is rough. Some sentences trail off. There's a section that just says "ASK ABOUT E1 vs E2 WHEN HEAT MATTERS."
6:15pm. Maya's back. She opens the note from this morning and cleans it up. Fixes the trailing sentences. Pulls up the textbook for the part she missed. Adds a section called "what I'm still confused about." Total time: maybe 25 minutes.
6:40pm. She clicks "generate flashcards" on the note. Picks the cards she wants — Fennie suggests around 18, she keeps 12. The dud cards (too generic, too obvious) get culled. The good ones go into her orgo deck.
6:45pm. She clicks "generate quiz" too. Ten questions, mixed format. She doesn't take the quiz now — that's tomorrow's job, when the material has had a night to settle.
Wednesday morning. Maya opens Fennie. Today's plan has four items: a 12-minute flashcard review (the new orgo cards mixed in with older ones, courtesy of spaced repetition), the orgo quiz from last night, twenty minutes on her physics problem set, and a chat session about her econ paper thesis.
That's the loop. Note → review → quiz → flashcard → plan → quiz again three days later → flashcard again next week. The note from Tuesday is still working a month later, when the material shows up on the midterm and Maya has actually seen it eight times instead of twice.
That's the difference between a note that sits and a note that compounds.
Why most students fail at notes
It's not because they don't take enough of them. Almost every student I've talked to takes plenty of notes. The failure point is downstream.
Three failure modes I see constantly:
The archivist. Beautiful notes. Color-coded. Hand-lettered headers. Treats the notebook like an artifact. Never gets tested on what's inside it. Spends Saturday morning re-watching lectures and thinking "I'm studying."
The dumper. Types furiously during class, captures every word, ends up with a 4,000-word transcript that's somehow harder to study from than the textbook. Opens it the night before the exam, panics.
The optimist. "I'll review these later." Later never arrives. Or it arrives the night before the final, when there are 240 pages of "later" to get through.
All three problems disappear when the note has somewhere to go. When clicking "generate flashcards" is faster than reorganizing your highlighter system, the math changes.
How to actually write notes Fennie can use
This isn't a markdown tutorial — there's a separate post for that. But there's a shape to notes that produces good quizzes and flashcards, and it's worth knowing.
Use headings as a chunking signal
## and ### aren't decoration. They tell the quiz generator where one concept ends and another begins. A note with one giant wall of text under one heading produces vague, wide-net questions. A note with five ### subsections produces five focused question clusters.
If you find yourself writing 600 words under one subheading, break it up. Future you, taking the quiz, will thank you.
Definitions deserve their own line
When you write:
**Nucleophile**: a species that donates an electron pair to form a covalent bond.
You're handing the system a perfect flashcard. Term on one side, definition on the other. The bold-colon-definition pattern reads as "this is a vocabulary unit" and the flashcard generator picks it up cleanly.
A messy version of the same idea:
A nucleophile is the thing that donates electrons, kind of, when there's a bond forming.
That works as a sentence. As a flashcard, it generates as "What is a nucleophile?" with an answer that's hedge-worded and wrong-shaped. The first version is a 30-second cleanup that pays off ten times.
Specifics over vibes
The quiz generator can only ask about what's actually in the note. If your notes say "the French Revolution had causes," you'll get a quiz that asks "what were some causes of the French Revolution?" and you'll write something vague and the quiz will accept it because there's nothing to grade against.
If your notes name the bread crisis, the Estates-General, the financial mess from the American war, the Tennis Court Oath — you'll get questions that test whether you know those things. Specifics in the input become specifics in the output.
LaTeX for math, every time
Inline: $f'(x) = 2x$. Block: $$\int_0^1 x^2 \, dx = \frac{1}{3}$$. Both render in the editor preview and in the generated flashcard. If you write math as plain text — f'(x) = 2x — it works, but it looks like a string of characters and the flashcard reads strange.
This matters more than people think. A flashcard with clean rendered math feels like a math flashcard. A flashcard with x^2 + 2x + 1 in monospace feels like a debugging session.
The Memory piece
Every quiz you take, every flashcard you rate, every note you skip — that goes into Memory. Memory is the eighth object, the one nobody talks about, and it's the reason the daily plan feels like it actually knows you.
If you keep getting the SN1 vs SN2 cards wrong, those cards get scheduled more aggressively. If you absolutely crush the IUPAC naming questions, those get spaced out. If you've been ignoring your physics note for a week and there's a midterm Friday, your Monday plan is going to lean physics-heavy, whether you wanted it to or not.
You don't configure Memory. You just use the system, and it builds a model of what you know, what you don't, and what you've been avoiding.
The note you wrote on Tuesday isn't sitting in a folder. It's a piece of evidence. Memory is reading it.
The two-click test
Whenever I'm helping someone set up Fennie, I run them through the two-click test. We open one of their existing notes — a real one, from a real class. We click "generate quiz." We look at the questions.
If the questions are sharp and specific and you'd actually want to answer them, the note is doing its job. If the questions are vague and you'd answer them with hand-waves, the note needs work.
It's a useful diagnostic because it removes the ambiguity. You can stare at your own notes for an hour and convince yourself they're "pretty good." A quiz won't lie to you. The questions you get back are an exact reflection of what's actually in there.
Three things usually fix vague notes:
- More headings, smaller chunks
- Real definitions, written as definitions
- Concrete examples instead of generic descriptions
That's it. You don't need to be a great writer. You need to write notes that have things in them that can be tested.
A few patterns that come up
A handful of things I've noticed students doing well, after watching a lot of people use the system.
Take rough notes in class. Clean them at night. Trying to write polished, structured notes during a fast lecture is a losing game. Capture during. Structure after. That evening cleanup pass — 20 minutes, max — is where the value gets created.
Pull questions out of your own notes. When you finish cleaning up an evening note, write down two or three things you're not sure about. Tag them with [ ] task checkboxes. They turn into tasks the next morning. Chat with Fennie about them. The conversation often reveals the gap.
Generate flashcards once per note, not once per topic. I see students try to make one mega-deck per class. It's worse than per-note decks. Per-note decks let Memory associate cards with the lecture they came from, which is how the spaced repetition gets sharper. Trust the small unit.
Don't keep every flashcard the generator suggests. The generator errs on the side of more. Cull aggressively. A 10-card deck of cards you actually care about beats an 18-card deck where four are noise.
What to do tonight
If you've read this far, here's the thing to actually do. Pick one note from today or this week. Open it in Fennie. Click "generate flashcards." Look at the deck. Cull the bad cards. Save the good ones.
Tomorrow morning when your plan loads, those cards will be in it. You'll review them in five minutes over coffee. Three days later they'll be back. A week later, back again, but spaced further apart because you'll be getting them right.
That's a note that doesn't just sit there.