Models can now read a novel in one go. That's a genuinely impressive feat of engineering, and it's led a lot of us, me included, to assume they remember it the way we would.
They don't. Lena's lead story explains what a context window really is, why material in the middle of a long document tends to get the least attention, and the simple habits that work around it. If you've ever had an assistant confidently describe a table that doesn't exist, this one is for you.
It pairs with a short, sharp lesson in compounding error: why a step that works 95% of the time becomes a coin toss when you chain twenty of them together.
Also this week: an Idea Autopsy of an AI tutor with 180,000 sign-ups and almost no students, and a practical etiquette for saying "I used AI".
— Maya
Also worth your time
- Missed Dev's webinar? The recording and the five-minute checking routine are on the events page. More than half of you caught the planted error. Dev claims it was a personal best.
- From Careers: "How do I show I'm good when AI writes half my code?" A student asks; a recruiter, a senior engineer and a six-months-in junior answer. Practical and kind.
- The Explain-It-Three-Ways Prompt. Jonah's favourite learning prompt from his teaching days: an analogy, a mechanism and a worked example, plus a test question.
- Next week: write your context file with us. Lena is running a live, hands-on workshop. Bring a laptop and leave with a finished draft. Details on the events page.
Prompt of the week
For long documents: make the model extract before it analyses. It's the single best fix for the murky middle.
From section {{section}} of the attached document ONLY, quote every
sentence that relates to {{topic}}, with page numbers.
Do not summarise or analyse yet. If there are no relevant sentences, say so.
One more thing
In our policy interview, Ilse Marchetti-Owusu said the most dangerous AI in your town is probably "the boring one making decisions about people that nobody has checked". It's the sentence our team has quoted most this month.