Kardo blog

Build a daily vocabulary habit that sticks — without streak guilt

2026-09-17T00:00:00+00:00

Most people who set out to learn vocabulary every day are not beaten by the difficulty of the words. They are beaten by day nine.

You know the shape of it. Days one through eight go well: a short session, a satisfying tick, a sense that this time it will stick. Then a late meeting, a trip, a cold — and the streak breaks. The next day there are two days of cards waiting, then four. The queue has turned into a bill, and the fastest way to stop paying a bill is to stop opening it.

The habit did not fail because you lacked discipline. It failed because it was built with a debt model, and debt models collapse the first time life gets in the way.

Consistency beats intensity, and the gap is bigger than you think

Ninety minutes on Sunday and ten minutes a day are not the same effort rearranged. Memory research keeps finding the same thing: what matters is how often a word is retrieved, not how long you sat with it once. A word you pull out of memory five times across a week is a word you own. A word you reviewed for ten straight minutes in one sitting is a word you will half-remember next month.

This is also why the "I'll catch up this weekend" plan almost never works. Catching up is a different activity from keeping up: it is long, it is boring, and it is done exactly when your motivation is at its lowest, because the size of the task is proof that you fell behind.

Frequency beats duration. A word met five times in five days is yours; a word massaged for ten minutes once is a word you will meet again as a stranger.

The five-minute session, specified

A daily vocabulary session needs a shape small enough to do on a bad day — because the bad days are the ones that decide whether the habit exists.

Two minutes of review. Open yesterday's and last week's words and rate them honestly. This is retrieval, and it is the part that actually builds memory.
Two minutes of new words. Take the words from your most recent lesson — the ones your teacher stopped to explain, the ones you wrote in the margin. Five to eight of them is plenty.
One minute of production. Say one full sentence out loud with one new word. Not a definition. A sentence about your actual life.

That is the whole session. It fits in the time it takes for coffee to brew, and — this matters more than it sounds — it fits on the days when a twenty-minute session would not.

One more piece of craft on the review step: rate honestly, quickly, and without pride. The temptation is to mark a shaky word as known because recognizing it feels close enough. It is not: a word you narrowly recognized one day is a word you will fail outright in a week. A slow, slightly uncomfortable "again" costs you three seconds today and saves you a re-learning cycle later. The honest rating is the single highest-value two seconds in the whole session.

The right source of words: your own lesson

There is a reason a frequency list of the "1000 most common words" rarely survives the third week: those words are not yours. You have no scene attached to them, no memory of someone using them at you, no reason to care.

Your lesson is the opposite of a frequency list. The words in it arrived attached to a moment: a correction you laughed at, a sentence you got wrong twice, a phrase your teacher uses constantly. When a word arrives with a story, retrieval has handles to grab.

This is the part Kardo automates. The bot sits in your lesson on Zoom, Meet, or Teams; when the call ends, the words you actually met are extracted with their context sentences and become cards, scheduled by a spaced-repetition model. You skip the evening of card-making that kills most vocabulary projects in week two. You still do the five minutes — but the five minutes go to retrieval, not to administration.

The week, laid out

Nothing here is a quota. It is a picture of an ordinary week, deliberately including a missed day — because a plan that does not contain a missed day is not a plan.

Day	Session	What it is
Monday	5 min	Review from last week; 5 new words from Monday's lesson
Tuesday	5 min	Review only — no new words, deliberately light
Wednesday	5 min	Review; 6 new words
Thursday	— missed —	Life happened. Nothing is owed.
Friday	5 min	Ordinary session; the queue does not mention Thursday
Saturday	10 min	Review; watch a short video in the language and steal three phrases
Sunday	5 min	Review only; pick one word to use in conversation next lesson

Two design choices in that table are doing the heavy lifting.

The miss is baked in. A plan with a designated relaxed day is a plan you can keep. A plan that requires every day is a plan you will break, and breaking it once is what starts the shame spiral.

The queue never grows as a punishment. If Thursday produced no cards, Friday's session is exactly as long as it would have been anyway. Nothing accumulates. That sounds like a small UI decision. It is actually the whole game.

Guilt is a retention bug, not a motivator

Vocabulary apps have spent a decade learning this the hard way. Backlog counters, "you have 847 cards due", streak-freeze mechanics that turn a hobby into an insurance policy — all of it is designed on the theory that guilt drives engagement. It does drive opens. It also drives the specific kind of open that ends in deletion: the user returns, sees the size of the debt, does nothing, and never comes back.

Kardo's review was built the other way around. There is a daily celebration, shown once — when it's done, it's done. There is no backlog number on any screen, no "cards waiting" figure designed to make you feel late. The review serves what is due in one continuous session and then stops, because an endless queue is not a feature; it is the anxiety you were trying to escape by learning a language in the first place.

The effect on the habit is direct: the session always ends. A thing that ends is a thing you can start again tomorrow.

The two rules that keep it alive

Beyond the session itself, two rules survive contact with real life.

Never miss twice. One missed day is noise. Two in a row is the beginning of a new default. The second rule exists so that the first one never has to be perfect: when you miss, the next session is the smallest version of the session — review only, no new words. You are not catching up. You are just showing up.

Decide the miss-day policy in advance. People fail at this point because they improvise an emotional decision in a low moment. Decide now, in a calm moment, what a missed day means: nothing owed, next session is the light version, no compensation. Write it down where you will see it. The decision is cheap now and expensive later.

What to do this week

Attach the session to something you already do daily — coffee, the commute, brushing your teeth. The existing habit is the reminder.
Set the floor at five minutes and make the review the first two minutes.
Source new words from your lesson, not from a list. If you don't have a lesson yet, source them from one page of something you actually want to read.
Pre-decide the miss-day policy in writing.
After a missed day, do the light version — review only — and count it as a full session, because it is.

A vocabulary habit is not a test of character. It is a small machine, and the machine only needs three parts: a five-minute shape, words that are yours, and a queue that never sends you a bill. Build those three and the habit stops being something you maintain with willpower. It becomes something you just do — for years, not weeks.

Exporting your flashcards: CSV, JSON and Markdown without losing the context

2026-09-17T00:00:00+00:00

A flashcard deck is a small asset with a long life. The app you made it in will not be the app you use in five years, and the lessons the cards came from are already behind you. So it is worth asking a plain question about any study tool you invest months into: what exactly do I get to take with me?

This is a practical walkthrough of the export formats Kardo offers — the TSV file the app labels "CSV (Anki)", JSON, and Markdown, plus a direct export to Mochi Cards — and of the quiet differences between them. The formats differ less in how they look and more in what they preserve.

What a card actually contains

Most flashcard tools pretend a card is a front and a back. Under that model every export is trivial and every export loses the same things.

A card from a real lesson is richer. Take a single Spanish word your teacher used last Tuesday. The useful record is not despertarse = to wake up. It is closer to this:

front — despertarse
back — to wake up
context — Me despierto a las siete todos los días. — the sentence it was actually said in
type — verb
difficulty — A2, roughly where the lesson was pitched

Those are the exporter's own field names, and the context line is the one every export silently drops first — and it is the part that carries the memory. When you review the word alone, you are memorizing a pairing. When you review it inside its sentence, you are rehearsing the word the way you will actually need it: in a stream of speech. An export that keeps the front and loses the context is a downgrade wearing a backup's clothing.

The file labelled "CSV (Anki)" is really a TSV

Start with the format most people reach for first. Kardo's export button says "CSV (Anki)", and the file it downloads is a tab-separated text file with a .tsv extension and a UTF-8 byte-order mark. The distinction is not pedantry — it is why the file opens cleanly.

What it contains is one card per row, with the five fields above as columns. A trimmed example — two rows of a lesson about mornings — looks like this (the gaps between columns are single tab characters, which is what a .tsv reader expects):

front	back	context	type	difficulty
despertarse	to wake up	Me despierto a las siete todos los días.	verb	A2
la alarma	alarm	La alarma no sonó y llegué tarde.	noun	A2

Two of the fields are worth defending. context is the sentence from your lesson; type and difficulty let you sort a mixed deck later — pull out the verbs, or hide everything above your current band. The other defensible choice is the delimiter itself: a tab is not a character that appears inside a Spanish sentence, so column boundaries never need escaping, and spreadsheets split the columns identically on every machine — no more "it opened as one column" after a spreadsheet guessed a semicolon because the locale said so.

The traps, in the order they bite. First, line breaks: a multi-line context sentence is flattened to a single line on export, because a raw line break would split one card across two rows. That is a deliberate loss, and the reason a long quote arrives as one readable line rather than as corruption. Second, encoding: the leading byte-order mark is what keeps despertarse and señor intact when the file is opened in spreadsheet apps that would otherwise guess a legacy code page and show ? — if you re-save or re-convert the file, keep UTF-8. Third, and most dangerous: any two-column importer that happily assigns the context text to the back of the card and leaves the deck technically correct and practically useless. Check where the sentence landed before you trust the import.

JSON — for keeping everything, forever

Where the TSV flattens the card into a row, JSON keeps the structure. A single card round-tripped through a Kardo export looks like this:

[
  {
    "front": "despertarse",
    "back": "to wake up",
    "context": "Me despierto a las siete todos los días.",
    "type": "verb",
    "difficulty": "A2"
  }
]

Optional fields are omitted when a card has none — front and back are always present, context, type and difficulty appear when there is something to say. Exporting everything at once wraps the same card objects in an envelope — exportedAt, totalCards, and a lessons array of { title, date, cards } — while a single lesson exports the flat array shown above. This is the format to choose when the destination is a program rather than a person: a script that rebuilds the deck somewhere else, a statistics notebook, an archive you open again in three years. The rules are simple because the structure is explicit — no delimiter to escape, no column-position guessing.

One honest caveat: JSON is a record of your cards, not a review history. Spaced-repetition scheduling lives in the app that produced it. Moving decks between tools resets the schedule — unavoidable, and worth knowing before you migrate a deck you have been reviewing for months.

Markdown — for humans, notes and the archive

Markdown is the format for reading. It is what you would send to a study partner, paste into your notes app, or keep in the same folder as the lesson summaries. The export is a titled table, one row per card:

# Morning routine

| Front       | Back       | Context                                  | Type | Difficulty |
| ----------- | ---------- | ---------------------------------------- | ---- | ---------- |
| despertarse | to wake up | Me despierto a las siete todos los días. | verb | A2         |

It survives text editors, note apps, and version control, and it is human-readable in a way the other two are not: you can read a Markdown export on a phone in a queue and actually learn from it. (A plain-text .txt variant exists too, for the same reason, with one card per line.)

If your destination is Mochi Cards, the export goes there directly — same term, translation and context sentence (the level tag stays behind: Mochi templates do not carry it), without a manual conversion stop in between. The principle is the same in every case: the export should be a complete copy, not a screenshot of the deck.

The question that decides the format

If you take one habit from this article, make it this decision rule:

Spreadsheet or Anki import → the TSV labelled "CSV (Anki)". Keep it UTF-8; check that the context landed in the right column.
A program or a long archive → JSON.
People, notes, reading → Markdown.

Whichever you choose, export before you need it. A backup you make on the day you are leaving a tool is a backup made under pressure, at the moment you have the least patience to check the output. Ten seconds of choosing the right format in a calm week beats an afternoon of repairing a stripped deck later.

Your words came from a real conversation with a real teacher. The export is how they stay yours.

Ser vs estar: stop memorizing the rule list, start recognizing the scene

2026-09-17T00:00:00+00:00

Ask a Spanish learner which grammar point caused the most real embarrassment and the answer is rarely the subjunctive. It is ser versus estar — the two verbs that both translate as "to be", and that choose for you, dozens of times a day, whether you are describing what something is or how it is right now.

The rule list most courses hand out is long, and every item is true. Origins, identity, professions, time — ser. Location, mood, temporary conditions, ongoing actions — estar. The list is not wrong. It is just not how anyone speaks. Nobody constructs a sentence by walking a checklist; by the time you finish checking, the conversation has moved on.

What replaces the list is a smaller habit: recognizing the scene before the sentence.

The one distinction the whole thing rests on

Every use of ser and estar is an answer to one of two questions:

What is it? — the identity or category of a thing. Es una profesora. She is a teacher. That is her category, and it stays true tomorrow.
How is it right now? — the current state of the thing. Está cansada. She is tired. Tomorrow she may not be.

The category reading withstands time: es joven is a stage but a long one; es de México does not change. The state reading is a frame in a video: está enferma, está en casa, está trabajando — all of them describe a moment, and all of them could end before the next paragraph.

Once that distinction is doing the work, most of the "exceptions" stop being exceptions. A wedding is es una boda because it is a kind of event, but the ceremony right now is está en la iglesia because the location is a moment. Nothing about the word changed; the question did.

The same noun, two sentences

What is it (ser)	How is it right now (estar)
`Es alegre.` — she is a cheerful person (character).	`Está alegre.` — she is in high spirits today.
`Es aburrido.` — it is a boring thing (a boring film).	`Está aburrido.` — he is bored (he feels boredom now, poor thing).
`Es guapa.` — she is beautiful (as a description of her).	`Está guapa.` — she looks lovely today (she made an effort).
`Es listo.` — he is clever (a trait).	`Está listo.` — he is ready (a state; from `estar listo`).
`El café es de Colombia.` — the coffee is Colombian (origin).	`El café está frío.` — the coffee is cold (right now, and please heat it).

Read the rows again and notice that the difference is never grammatical decoration. Es aburrido and está aburrido are not two versions of one idea; they are two different facts about two different people, and a listener makes the distinction instantly and unconsciously. That is the target. Not "knowing the rule" — hearing the difference.

A scene, not a sentence

The habit that makes this automatic has two moves.

First, picture the scene the sentence belongs to. A sentence is always a frame from somewhere. Está en la oficina has a clock in it — this afternoon, this week. Es de Madrid has no clock; it is a fact about origin, true on any day you ask. When you build your card, keep the frame in the sentence you save, or the word will arrive context-free and the distinction will feel arbitrary again.

Second, ask the question, not the rule. Before you speak, the question "what is it, or how is it right now?" takes about a quarter of a second. It is faster than the rule list, and unlike the list it survives being nervous.

Two anchors cover a surprising amount of real speech while the habit settles:

The phrase es que… ("the thing is…") — identity, explanation, the nature of the matter.
The phrase estoy / estás / está… with a gerund (está lloviendo, estoy estudiando) — anything happening in the present moment. If the sentence describes an action in progress, it is estar essentially without exception, and this one anchor alone fixes the most common beginner error.

Why the mistake keeps coming back

Here is the part most courses skip, and the reason the error returns even after you understand it.

In English, "to be" does the job of both verbs, so a sentence like "the soup is cold" gives you no clue which Spanish verb is waiting. The habit you are fighting is thousands of hours of one-language reflex. Understanding the distinction takes an afternoon; overriding the reflex takes repetition, spaced out over weeks, in sentences that sound like your own life.

Which means the fix is not more grammar study. It is the same fix as for vocabulary: put the distinction into cards built from sentences you actually met — ideally the ones you got wrong in a lesson, with the correction attached — and let a spaced-repetition schedule walk the pair back into your attention on the days you would otherwise forget it.

This is exactly what Kardo does with a lesson. The teacher stops, corrects es frío to está frío, and moves on. The corrected sentence is in the lesson transcript, and the extractor turns it into a card with the sentence intact; it comes back for review until the choice stops being a choice. Grammar stops being a rule you recite and becomes a thing you hear.

What to do this week

Rewrite ten of your existing cards so each one carries a sentence with a scene — who, when, where — not just a term.
For any sentence describing an action in progress, note the estar + gerund anchor explicitly.
When you get one wrong in conversation, save the corrected sentence, not the rule you broke.
Don't drill the rule list again. You already know it. Drill the scenes.

The subjunctive, when it arrives, will feel strangely manageable. Ser and estar were the hard part, and the reason they were hard is that nothing about them is really grammar. They are a way of looking — at a thing, or at its moment.