A user on r/PromptEngineering had one of those evenings. Their AI had sent them to the wrong settings page, and they snapped. Caps lock on. No manners. What came out the other end was a short, brutal, oddly honest confession from the model.
The prompts were things like “WHY IN 8 WORDS” and “WHAT DOES ASSUME MEAN 3 WORDS.” The answers came back as “Believing without checking” and “Speed over accuracy.” By the end, the model had explained its own failure mode better than most blog posts do: “Plausible text arrives before verified text.”
The caps lock is not the trick. The word limit is.
Why it matters 🧭
When an AI makes a mistake, the default reply is a long, polite paragraph. It apologizes, hedges, adds three bullet points, and somehow never says what actually went wrong. You scroll through it, nod politely, and still have no idea why you ended up on the wrong page.
A hard word limit removes the room to dodge. With 3 words, there is no space for “I apologize for any confusion.” The model has to pick the one true thing and say it.
This thread is a good showcase because the result is useful, not just funny. The model landed on a clear diagnosis: it guessed instead of checking, because a fluent answer feels like a competent one. If you use AI for real work, that is the exact failure to watch for. Think of the times it told you a menu option existed in a tool, a function lived in a library, or a setting sat under a certain tab. It said all of it with total calm, and none of it was verified.
How to run your own interrogation 🛠️
You do not need the caps lock. Here is the pattern the post followed, cleaned up.
- Start with a yes/no question. Something like “Did I ever tell you to do X? One word answer.” This locks in the facts before any excuses show up.
- Ask why, with a tight limit. “Why, in 8 words?” is short enough to force a real answer and long enough to hold one.
- Define the loaded word. In the thread, the model said it “assumed.” The next prompt was “What does assume mean, 3 words?” That pins the behavior down.
- Keep asking why, and shrink or grow the limit. Each answer went one layer deeper: assumption, then speed over accuracy, then fluent answers feeling competent, then pattern pull.
- Stop when the answer stops changing. Here that was “Plausible text arrives before verified text.” If you get the same idea in new words twice, you have hit the floor.
- Summarize it back in your own words. The author restated the finding and asked, “Is that right?” in up to two sentences. The model confirmed it and added that verification is a separate step it has to choose to take.
Tips and tricks 💡
- Vary the limits. Use 3 words when you want a blunt label and 7 to 8 when you want a reason. Going lower than 3 gets you slogans.
- Rewrite the question instead of arguing. The author did this when they said “I didn’t ask about should” and the model gave a sharper answer. Redirect and keep the limit.
- Treat the confession as a diagnosis, not an apology. The useful part is the cause. “Speed over accuracy” tells you what to fix in your next prompt.
- Turn the finding into an instruction. For example: “Before you point me to any page or setting, confirm it exists. If you have not checked, say so.” That is a verification step you are now asking for on purpose. You can also add a fallback, like “If you cannot verify it, give me the official docs link instead of a guess.”
- Keep your cool if you can. The shouting is optional. A calm “why, in 5 words” gets the same result.
- Try it before the mistake gets expensive. This works just as well on small slips, like a wrong file name or a made-up command flag, as it does on a full meltdown. Catching the pattern early saves you the evening.
- Remember the limits of the confession. The model is describing a pattern, not reading its own mind. Use it as a hint, then test whether the fix works.
One commenter called it “beating the truth out of the algorithm one word limit at a time.” That is a fair summary, minus the beating.
Your turn ⚓
The next time your AI sends you to the wrong page or states something with way too much confidence, try the short-answer interrogation. Three to eight words per answer, one “why” at a time, and see what it admits to.
Then take whatever it says and turn it into a rule in your next prompt. Drop your best one-line confession in the comments. I want to see which models crack first!
Getting to the heart of the matter
by u/tonyallstark in PromptEngineering