Muse English is a free English learning app with daily lessons across all 6 CEFR levels (A1 Beginner to C2 Proficient). Every day brings new vocabulary, a real podcast conversation, shadowing practice, grammar and quizzes β all at museenglishapp.com.










Listen to todayβs conversation.
Welcome back to Word Kitchen, the show where we cook up the vocabulary you need for fluent, fearless English. I'm Maya.
And I'm Lena. Today we're serving a full menu from the world everyone is talking about, artificial intelligence. Ten delicious new words, and Maya, fair warning, today's list is gloriously nerdy.
Nerdy is good. Nerdy is the new fluent. Here's the menu: enshittification, agentic, multimodal, tokenization, watermarking, sandboxing, quantization, zero-shot, vibe coding, and model collapse. Don't panic. We'll take them one plate at a time.
Let's start with the spiciest one, enshittification. It's the process by which an online platform gradually declines in quality as it starts prioritizing profit over its users' experience.
Exactly. Think of your favorite social app three years ago. Clean, useful, fun. Then the ads multiplied, the feed got weird, and suddenly everything was a sales pitch. That's enshittification in slow motion.
It was coined by the writer Cory Doctorow, and it usually runs in stages. First the platform is good to users, then it abuses users to please business customers, then it abuses everyone to please shareholders. Classic enshittification.
And once enshittification sets in, it is brutally hard to reverse, because the incentives never point back toward the user. Users leave, the product gets emptier, and the whole thing just limps along on lock-in.
So the honest question for every AI startup today: are you building something that lasts, or are you three funding rounds away from your own enshittification?
Next up, agentic. An agentic AI system is one that can act independently, pursuing goals and completing tasks on its own rather than waiting for every instruction.
So the difference between a chatbot that answers questions and an agentic assistant that actually does things. My calendar got sorted by an agentic assistant this morning. It booked the dentist, rebooked my flight, and apologized for the double charge, all before my coffee was ready.
That's the promise, and honestly it's thrilling. The more agentic these systems become, the less we have to micromanage every tiny step.
But agentic systems also raise the stakes. When software can act on its own, a small misunderstanding can cascade into a very real mess, which is why control and oversight have to grow at the same pace as the agentic ambition.
Exactly. Agentic is powerful, but power without brakes is just a crash waiting for a date.
Now multimodal. A multimodal model understands and produces several kinds of input at once, text, images, and audio, instead of living in one medium.
This is the one that changed my workflow most. I show a multimodal model a photo of my fridge, and it plans dinner, writes the recipe, and narrates the steps while I cook.
And classrooms are going multimodal too. Students point their phones at a whiteboard, and the multimodal tutor explains the diagram in plain English, in their own accent.
The truth is, humans are multimodal creatures. We talk, we gesture, we sketch, we listen. So a multimodal assistant just feels more human, because it meets us in every channel at once.
And that's why every serious lab now treats multimodal as table stakes. Single-medium models are starting to look like silent films next to talkies.
Let's go under the hood for a minute. Tokenization is the process of splitting text into small pieces, called tokens, that a language model can process.
Right. Models don't actually read words the way we do. Thanks to tokenization, they chop language into chunks, sometimes whole words, sometimes fragments, and work on those.
Good tokenization is invisible, but bad tokenization is hilarious. Without careful tokenization, a model might split a surname into nonsense pieces and then cheerfully mispronounce it forever.
Subword tokenization is the clever part. It lets models handle rare words gracefully by breaking them into familiar pieces, so nothing is truly out of vocabulary.
So behind every smooth answer sits a quiet, diligent tokenization step, slicing your sentences into bite-sized tokens before the magic happens. Remember that word, because it comes up again later.
Speaking of hidden machinery, watermarking. That's embedding hidden signals in AI-generated content so it can later be identified as machine-made.
Why does it matter? Because when anyone can generate a perfect fake, watermarking gives journalists, teachers, and regulators a fragile but useful tool for spotting synthetic content.
Fragile is the key word. Researchers keep showing that determined attackers can strip or forge the watermarking signals, so watermarking is a speed bump, not a wall.
Still, I support serious watermarking standards. If a student submits an essay or a campaign posts a video, we deserve to know whether watermarking tells us a machine was involved.
And as the generators get better, invisible watermarking may be the only honest difference between a photograph and a fabrication. That little hidden mark carries a lot of weight.
Now sandboxing. That's running software in an isolated, controlled environment to test it without risk, like a playground with very high walls.
My favorite example: security teams catch a suspicious attachment and, instead of opening it like a thriller villain, they drop it into a sandbox. Sandboxing means the malware thinks it won while it's actually stuck in a cage.
AI labs do sandboxing too. Before a new model touches the real world, they let it run wild inside a sandbox to see what it would try to do.
And it's just good engineering hygiene. Proper sandboxing separates the experiment from everything you love, so a bug costs you an afternoon, not your company.
So sandboxing is the difference between brave and reckless. Brave tests the lion. Reckless opens the cage. Choose sandboxing.
Then there's quantization, one of my favorite words to say at dinner parties. It means compressing an AI model by using simpler numbers, trading a little accuracy for much smaller size and faster speed.
The result is wild. Through quantization, engineers have squeezed flagship models onto laptops and even phones, with barely any loss in quality.
I love what quantization means for access. A student in a village with a cheap phone and no cloud account can run a smart assistant locally, thanks entirely to quantization.
The trade-off is real, though. Aggressive quantization can make a model dumber in subtle ways, so labs tune it carefully, shrinking the numbers without shrinking the brain.
But done well, quantization turns a data-center giant into a pocket companion. Smaller, faster, greener, and yours.
Next, zero-shot. A zero-shot model can handle a task it was never explicitly trained to do. No examples, no fine-tuning, just cold.
That still blows my mind. I asked a model to classify ancient pottery by culture, zero-shot, something it had no training for, and it nailed it.
The zero-shot leap is what made large language models feel like magic. Older systems needed thousands of labeled examples. A zero-shot model just reads the instruction and goes.
Of course, zero-shot doesn't mean zero-error. A model going zero-shot can be confidently wrong, so for anything critical, we still check the work.
Fair. But the trend is clear. Zero-shot ability keeps climbing, and tasks that needed custom training last year now run zero-shot on a phone.
Okay, now the cultural phenomenon: vibe coding. That's writing software by describing what you want in plain language and letting AI generate the code.
It has completely changed who gets to build. A designer with an idea can go vibe coding on a Friday afternoon and have a working prototype by dinner.
The purists are horrified, of course. They say vibe coding produces spaghetti and that you'll regret every line you didn't write yourself.
There's truth in that. Vibe coding shines for prototypes and side projects, but for systems that carry real responsibility, you still want an engineer reading the code.
And honestly, vibe coding is just the latest chapter of an old story. Compilers, frameworks, no-code tools, each one was called cheating by the previous generation, and each one let more people build.
So vibe coding isn't the death of programming. It's programming with a louder imagination.
Which brings us to the sobering finale, model collapse. That's the degradation of an AI model trained mostly on AI-generated data.
Think about it. The web is filling up with machine-written text. If future models train on that output, they start learning from echoes of themselves, and model collapse sets in, each generation a little blurrier, a little more generic.
Researchers have actually measured model collapse in the lab. Feed a model its own outputs for a few rounds and it forgets the rare, strange, beautiful edges of language, collapsing toward the average.
That's why high-quality human data has become precious. Preventing model collapse is now a strategic priority for every lab, because the training data of tomorrow depends on real human writing today.
So here's the twist, Maya. Every essay, every podcast transcript, every weird blog post a human writes is now part of the defense against model collapse. Human creativity is infrastructure.
I love that. Keep writing, everyone. You're training the future, and apparently you're also stopping model collapse while you're at it.
Let's run the menu one more time, chef's tasting style. Enshittification, the slow rot of platforms that chase profit over people.
Agentic, software that acts on its own, with ambition and a need for brakes.
Multimodal, AI that sees, hears, and reads in one go.
Tokenization, slicing language into tokens behind the scenes.
Watermarking, the hidden marks that say a machine made this.
Sandboxing, the safe playground where experiments can't hurt anyone.
Quantization, shrinking giants into pocket-sized helpers.
Zero-shot, solving new tasks with no training wheels.
Vibe coding, building software on pure imagination and plain words.
And model collapse, the blurry echo we avoid by staying human.
Use them this week, all ten, in real conversations. That's how words move from your notes into your voice.
This has been Word Kitchen. I'm Maya.
And I'm Lena. See you tomorrow with a fresh menu.
Listen and repeat along with the studio audio. Full shadowing practice with pronunciation scoring is in the app.
1. Sara founded her startup to fight enshittification before it ever touched her users.
2. She had watched beloved platforms decay into enshittification, and she refused to repeat the pattern.
3. Resisting enshittification was the whole business model, her investor deck said on page one.
Shadow every sentence with studio audio and get your pronunciation scored β only in the Muse English app.
Reported speech tells us what someone said, without quoting their exact words. When the reporting verb (**said**, **told**, **asked**) is in the past, tenses usually shift back β this is **backshift**. The shifts are systematic: present β past, present perfect β past perfect, **will** β **would**, **can** β **could**, **may** β **might**, **must** β **had to**. You do NOT always backshift. Keep the original tense for general truths or facts still true now, and when you report something immediately after hearing it. **Say** takes no person: she **said** she was tired. **Tell** takes a person
Get clear explanations, more examples and interactive exercises.
New lessons, podcasts and quizzes daily β free in the Muse English app.