Fluency Is Pattern Recognition
Pierre Teo · Published
This is my working mental model for second language acquisition — built from my own journey (in-person lessons, Duolingo), binging Steve Kaufmann videos, reading Stephen Krashen on comprehensible input, and going back and forth with AI to pressure-test all of it. It's what I'm applying right now learning Japanese.
Fluency isn't knowledge, it's pattern recognition — and you train it the way you'd train any skill: massive exposure, plus practice for the mouth that actually produces the speech.
My goal is conversational fluency — understanding spoken language and participating in conversation. Not reading literature, not writing essays. Handwriting especially feels less relevant every year; you could argue typing on a phone matters more than writing by hand now. But I digress. Conversation is the target.
What does conversationally fluent actually mean?#
It comes down to one thing: automaticity.
It's the point where you don't actively construct sentences word by word — no pausing to work out past tense versus present tense, no hunting for the word you need, no mentally rearranging the sentence into the right order before it leaves your mouth. Where you hear something and the meaning arrives whole, without you attending to individual words. If you're still consciously assembling, you're not there yet. Automaticity takes away the chore of parsing and assembly, and leaves you thinking only about what you want to say — not how to say it.
Our brain has two separate memory systems, running on different circuits. Declarative memory stores facts and rules you can consciously access — the stuff you can recite. Procedural memory stores the automatic patterns underlying fluent behavior — the stuff you just do, like riding a bike or typing without looking. Real-time speech runs on procedural memory. You can know every conjugation rule declaratively and still freeze mid-sentence, because conversation happens too fast for conscious lookup. Fluency isn't stored where facts are stored.
This changes what "studying" should mean. Most traditional methods — grammar drills, memorized rules, vocabulary lists — deposit knowledge into declarative memory and hope it transfers. It largely doesn't, at least not directly — the circuits are different. At best, knowing a rule primes you to notice that pattern in real input, and the noticing is what does the work. Procedural memory is trained the way skills are trained: through repeated exposure and repeated doing. That's what the rest of this method is built around.
Getting there means three things: tune your perception, train your brain to recognize incoming speech, train the muscles that produce it.
Step one: tune your ear and mouth#
Run through the writing system, and for each letter or character, try to replicate exactly what it sounds like — not what the romanization suggests.
This is where most people go wrong from day one. Romaji and transcriptions are written in English letters, so people pronounce the sounds the way they would in English. But that's a wrong interpretation, and they get stuck with it forever — that's where non-native accents come from. English letters simply don't represent many of the target language's sounds well. (Same problem if your reference language isn't English.)
Run the sounds as many times as you need to build a good sense of them. How deep you go is up to you — master them up front if you like. What's important is establishing a correct reference: actually noticing what each sound is, especially where it differs from what your native language would predict. The reference doesn't need to be perfect on day one — you'll keep refining it every time real speech surprises you.
This works surprisingly well: give an AI the entire writing system and ask, for each character, what's the closest approximate sound in English and where the approximation breaks down. And there's no need to overthink the mechanics — you're looking for the shortest, easiest path to producing the sound, not memorizing tongue positions and mouth diagrams. Hear it, attempt it, compare, adjust. Your mouth will find the configuration on its own.
Step two: lots of comprehensible input, plus shadowing#
Listen to speech you can mostly understand — dialogues, conversations, stories, anything where you're following the meaning of what's being said. Not just hearing the sounds: trying to make sense of how each word builds the meaning. That's what does the work. Follow along with transcripts when it helps. Look things up when you're lost. The goal is comprehension, not analysis — you're not memorizing vocabulary or studying grammar rules. This lets your brain pick up the patterns on its own, unconsciously, the same way it picked up the patterns of your first language before you knew what grammar was.
What counts as "mostly understand"? If you're catching the gist — the general shape of what's being said even when individual words escape you — you're in the right zone. If it's complete noise, find something easier. If it's effortless, find something harder. The sweet spot is where comprehension requires effort but succeeds, where you're stretching slightly beyond your current level.
Then shadow it — say it out loud, copying everything: the individual sounds, the length of each one, the rhythm and melody of how the speaker says it. It's more like doing an impression than reciting a transcript. Shadowing builds the motor patterns, the muscle memory.
Meanwhile, underneath your awareness, your brain is quietly keeping count: which sounds follow which sounds, which words show up together, which phrasings appear in which situations. Every hour of comprehended input gives it thousands more examples to learn from.
What not to do#
Don't study grammar. Grammar rules go into declarative memory — the recite-facts system, not the produce-speech system. Grammar rarely crosses your mind while speaking your native language: never during, occasionally after, retrospectively checking whether what came out was right. That's the order we're building — intuition first, rules as an afterthought. Some grammar knowledge helps with understanding. It just won't make you speak.
Don't grind flashcards. Useful for making content more accessible — more words recognized means more input is comprehensible. But there's a catch: flashcards feed declarative memory, and words banked there won't reliably surface in natural speech on their own. They have to be re-encountered in real input before the procedural system owns them.
Don't rush into conversation practice. Conversation isn't where fluency gets built — it's where patterns you already own get switched on for production, and where you test yourself and notice your limits. That's why it works late and backfires early. Early on, your brain isn't ready: you'll be translating in your head, using exactly the wrong mental pathway, and rehearsing your mistakes. Later, once listening has laid down the patterns, a surprisingly small amount of conversation activates them. Feeling ready isn't the signal, either — that feeling never comes. A better cue is catching yourself mentally forming replies while listening. (For what it's worth, researchers still argue about how much speaking practice drives learning versus just polishes it — but almost nobody disputes that massive input is the foundation.)
It's not linear#
The early weeks can feel discouraging. You catch fragments, miss connections, replay the same thirty seconds over and over. This is normal. What's happening underneath — the gradual strengthening of pattern recognition — isn't something you can feel in real time. But it's happening. Weeks later, you'll notice you're catching phrases you used to miss, following conversations that used to be noise. The comprehension didn't arrive in a single moment. It accumulated across all those sessions that felt unproductive.
This is also why brief daily sessions compound over months in ways occasional marathon sessions can't match. A big bottleneck is consolidation, and consolidation happens during sleep: the patterns you encountered during the day get replayed, sorted, and wired in overnight. Each night does work for you that you can't get any other way. More hours per day still helps — immersion works precisely because it's massive input sustained daily — but the days are the multiplier. A short stretch of focused listening every day gives the consolidation cycle steady material to work with. The regularity matters more than the duration. Learning a language takes calendar time, not just clock time.
Why I recommend Duolingo#
I'm using Duolingo for Japanese right now, and it's excellent. I know that's an unfashionable thing to say. Duolingo is the mainstream option, and dismissing the mainstream is an easy way to feel discerning — "real learners" use textbooks, tutors, anything but the green owl. But the standard criticism, that it's a toy that only gets you to a beginner level, describes an app that no longer exists. Duolingo in 2026 is a different beast, rebuilt around the latest AI: its nine major courses — covering roughly 90% of learners — now extend to B2, which is more than everyday conversational fluency requires.
The streaks, leaderboards, and animations draw mockery too — written off as childish gimmicks, dopamine tricks that farm engagement instead of teaching. But they make the app a genuinely great experience, and they solve the actual hardest problem in language learning: making you come back and put in the hours, day after day. (Most of the language learning that actually works is really boring to most people.)
And the pedagogy is better than the internet gives it credit for. It doesn't front-load grammar. Lessons are built around everyday topics and scenarios, and they feel like games pitched at the ideal difficulty — not easy, not impossible, always achievable. There's plenty of listening. Speaking is built in: it makes you shadow, it makes you talk through calls. New words arrive at what feels like an optimal rate. This is exactly what you'd expect from a company with an army of second language acquisition PhDs building the curriculum. They know what they're doing, and it works — no other app I've seen does this. Two weeks in, I feel a noticeable difference. My only criticism: the content isn't the most exciting.
The Destination#
Here's what the destination looks like: one day you'll follow a conversation without thinking about it. You'll respond before you've consciously decided what to say.
And you won't be able to point to the session where it happened, because it didn't happen in any single session. It happened across all of them, in hundreds of unremarkable days that each felt too small to matter.