Ask a room of learners whether they understand the difference between what a chatbot knows and what it remembers, and every hand goes up. The words are ordinary. The distinction sounds obvious.
Then ask which of the two is doing the work when a customer says and what about the other one? — and the hands come down.
That space, between the idea a learner can nod at and the idea they can use, is where most teaching about AI quietly fails. Someone explains a concept, shows a diagram, runs a demonstration that works, and the room agrees. Agreement is cheap. Nothing has been asked of anybody yet, so nothing has been revealed.
The camp was built to stop that gap staying hidden. Its method was immersive in a particular sense — not immersive as in elaborate, but immersive as in you are inside the consequence. Roles rotated, so nobody could watch somebody else code. The client was real, and would read the result. The sample code had been broken on purpose. And the assessments were designed to expose what campers had not understood rather than to confirm what they had.
Teaching that way has a cost: it surfaces problems a lecture would have left buried, and then somebody has to deal with them. In week two the camp paid it.
What the Kahoot exposed
There is a distinction the whole programme turns on. Knowledge is what a system can look up. Memory is what it carries forward through a conversation. Confuse them and you build a bot that either forgets who it is talking to, or invents what it should have retrieved.
A Kahoot revealed that the cohort had not got it. The scores came back and the gap was not a few campers having an off morning — they did not understand memory, and had not understood it for some time.
By day six the verdict was blunt: We need to take a whole lesson on memory … the students don't understand it.
Losing a day on purpose
What happened next is the part that matters. The lesson stopped and the concept was re-taught on the spot, at the cost of the day's plan. In a programme running to a fixed twenty-day schedule with a fixed showcase date, that is an expensive decision. It was made anyway.
The re-teach also changed method. Terbry Lewis, a facilitator from Saint Lucia, seeded the sample code with deliberate errors — one or two, introduced on purpose — so that campers could not run it and move on. They wrestle with it, he said, which was nice.
That is the immersive principle applied to a repair rather than a lesson plan. A camp can explain memory in ten minutes. What it cannot do in ten minutes is give someone the experience of having been wrong about it, which is the thing that actually sticks.
Try it yourself
Reading a definition is not the same as feeling the difference. The campers did not learn this from a sentence — they learned it from getting a question wrong in front of each other, and then from code that would not run until they understood why.
So before you go on: take the question, then switch a bot's memory off and watch a conversation that was working a moment ago fall apart.
Your turn
A customer asks a bot for their account balance. Three messages later they ask, “and what about the other one?” What does the bot need to answer?
Switch memory off
I'm on Carriacou.
Noted — Carriacou. How can I help with your water service?
Is there an outage today?
Yes — a scheduled interruption on Carriacou until 4pm.
And tomorrow?
Nothing scheduled for Carriacou tomorrow.
With memory, the island is established once and carried forward. Every later answer inherits it.
A teaching illustration written for this publication. The question is not one of the camp’s actual Kahoot items, and the conversation is constructed rather than a transcript — but the distinction it turns on is the one day six exposed.
What it bought
Every grounded answer, every source-checked claim and every context-preserving language switch later in this book rests on a cohort of teenagers having got this distinction straight in the second week.
They did — because someone was willing to lose a day.