In this corner, weighing in at a metric fuck-ton of high-tech weaponry including an undisclosed number of thermonuclear warheads, the winners of more Nobel prizes than they bother to count, a place where every last citizen is a trained soldier... surrounded by enemies, they've never lost a war since the fighting started the first day they were born... I give you, the mighty Lion of Judea... the embarrassment of the entire Arab world... ISRAEL!!!!!
and... in this corner, weighing in heavy, carrying only a bag of rocks... I give you the people no one wants, but everyone loves... from the country that never even existed... they've lost each and every fight they've ever picked.... the princes and princesses of pity... the lords of the lost cause... champions in their own mind... the Muslim brothers of some other mother... the masters of their own disaster.... PALESTINE!!!
Try hiring Claude and Gemini... when I vibe-code with those three all at once in a joint development session - the results are astonishing... If you guide them toward creative solutions and away from this instinct to be super-efficient but banal... Presto, Shazzam, WonderTwin powers activate... seriously.
@BenjiBacker Is it okay to microwave something for my guests or do I need to use only the stove? Can I order in a side dish and not disclose I didn't make it?
Not all. Credit where credit is due: Prof. Michal Kosinsky of Stamford (doing work at the intersection of ML and Social Psych) posited, in a not too thinly veiled point that it would not happen like that at all... and, if you ever spoke with him on this topic, he might have extended the core finding about Theory of Mind presented in this paper of his and comment that it could even emerge entirely unnoticed.
https://t.co/GJWXUGYv3K
Eric, hopefully you know clearly how clear this has become to the great unwashed masses scuttling around in our little patterns which have nothing to do with the straight and narrow of academic halls. I put on my captain obvious hat to annotate that post.
Love,
Lots and lots of us.
Two? No measurement or calculation error regarding the ratio itself is possible, eh? That science may not be able to correctly identify that ratio in the first place seems rather more likely than either of your answers. For that matter, perhaps the imbalanced equation you are trying to explain away is deeply flawed and there is a yet-to-be-discovered third type of positive-mass-bearing particle...
How is it that you can't seem to acknowledge that it is not possible to know what you do not know - but failing to even consider there are unknown unknowns is the well-spring of the torpor that has left us without meaningful theoretical progress in about a century. It's also why you don't have to be a physicist to see, as is obvious to anyone familiar with basic human psychology, who is suffering and insufferable as well as ignorant in this conversation. There is one certainty... that the ground truth of the situation is not obvious enough and therefore embarrassing enough to mitigate the ego mechanisms which, ironically continue to prevent you from seeing the ground truth.... I'm quite certain that a deep dive there would be an interesting clinical case study.
Two? No measurement or calculation error regarding the ratio itself is possible, eh? That science may not be able to correctly identify that ratio in the first place seems rather more likely than either of your answers. For that matter, perhaps the imbalanced equation you are trying to explain away is deeply flawed and there is a yet -to -be-discovered third type of positive-mass particle... Eric's point is that you can't seem to acknowledge that it is not possible to know what you do not know - but failing to even consider there are unknown unknowns is the well-spring of the torpor that has left us without meaningful theoretical progress in about a century. It's also why you don't have to be a physicist to see, as is obvious to anyone familiar with basic human psychology, who is suffering and insufferable as well as ignorant in this conversation.
There is one certainty... that the ground truth of the situation is not obvious enough and therefore embarrassing enough to mitigate the ego mechanisms which, ironically continue to prevent you from seeing the ground truth.... I'm quite certain that a deep dive there would be an interesting clinical case study.
Claude gives you 30 memory slots, 200 characters each. That's 6,000 characters of persistent context — the only information it carries into every new conversation for free, with zero processing cost.
Most people write English sentences in them. Things like: "I'm a software engineer who prefers Python and works at a fintech startup in Austin."
That works. But it's like using a filing cabinet to store one piece of paper per drawer.
Here's what we did instead — and it expanded Claude's effective working memory by roughly 4-5× while cutting its need to search for context by about 70-80%. Anyone can do this in about 20 minutes.
THE CORE INSIGHT
Claude doesn't read memory slots like you read a page — top to bottom, left to right, parsing grammar. It processes the entire system prompt through parallel attention. Every token activates simultaneously, weighted by relevance to the current conversation.
This means grammar is waste. Articles, prepositions, punctuation for human readability — all of it consumes characters without adding information Claude can use. What Claude needs is distinct, unambiguous tokens that fire when relevant.
So instead of English, build a symbolic language.
STEP 1: THE SYMBOL VOCABULARY
Create a small set of symbols with fixed meanings. These should be visually distinctive (Unicode symbols work great because they're rare tokens — they stand out in the attention weights more than common English words).
Here's ours:
→ causes / leads to
⊘ blocks / prevents
⇒ therefore / implies
↔ mutual dependency
∆ needs fix / change needed
✓ done
⏳ pending
✗ killed / rejected
🔴 important
⚡ time-urgent
⚠ caution
◉ milestone target
⟳ recurring / cyclical
¬ not / negation
≈ approximately
∅ empty / none
∵ because
And the critical one:
» more detail stored elsewhere — go look it up
More on that last one in a minute.
STEP 2: SHORTCODES FOR YOUR DOMAIN
Create 2-3 letter codes for the categories that matter to your work. Don't overthink it — just cover your main buckets:
Lg = legal
Fin = finance
Pr = product
Mk = marketing
Sl = sales
Rk = risk
Op = operations
Wb = web/digital
Inf = infrastructure
Vnd = vendor/3rd party
Ins = insurance
Pri1/2/3 = priority tiers
If you have recurring people, give them single letters: J = James, S = Seth, etc.
STEP 3: THE ROSETTA STONE
Your first memory slot (or first two, if your vocabulary is large) MUST contain the legend — the decoder for everything else. Without it, a future conversation sees raw symbols with no guaranteed way to interpret them.
Ours looks like:
LEGEND1:→causes;⊘blocks;⇒implies;↔mutual;∆fix;»MCP-query;✓done;⏳pend;✗no;🔴impt;⚡urgent;⚠caution;◉milestone;⟳recurring;¬not;≈approx;∅none;∵because
That's one slot. Every other slot in the system is now readable.
STEP 4: COMPRESS EVERYTHING
Take any English sentence:
"The website development folder is completely empty, which is a critical gap. We have a Site Build folder with 97 files and the landing page is complete. A Fiverr designer is working on it but hasn't delivered yet."
Becomes:
Wb⚡🔴:dev-folder=∅crit-gap|SiteBuild:97files,landing✓|threat-brief-HTML✓|Vnd-Fiverr⏳
The English version is 234 characters — over the slot limit. The symbolic version is 78 characters, fits easily with room for more facts, AND it carries metadata (urgent, important, vendor-tagged) that the English version doesn't.
Pack 3-5 facts per slot using | as a separator. Each slot becomes a dense packet of related information.
STEP 5: THE » TRIGGER
This is the real unlock.
If you use any external memory system (an MCP memory server, a notes app Claude can search, a knowledge base attached to a Project), the » symbol tells Claude: "I have the summary right here in working memory — but there's deeper detail stored elsewhere. Go fetch it if this becomes relevant."
Without »: Claude either has the full detail in the slot (impossible at 200 chars) or doesn't know it exists.
With »: Claude has enough context to know WHAT exists and WHERE to look, but doesn't burn processing power looking it up until the conversation actually needs it.
It turns 30 memory slots from a tiny notepad into an index for unlimited storage. RAM pointing to hard drive.
WHAT THIS ACTUALLY DOES
Before: ~35-45 English facts across 30 slots. Claude starts most conversations by making 3-5 search queries to rebuild context, burning context window tokens, which makes conversations compact (lose history) faster.
After: ~120-140 symbolic facts across 30 slots. Claude starts conversations already knowing the key facts, only queries for depth when » triggers on a relevant topic. Conversations last roughly 20-30% longer before compacting.
The activation precision improvement is harder to quantify but real — rare Unicode symbols create cleaner attention patterns than English words that appear thousands of times in training data. When Claude sees ⊘, it means exactly one thing. When it sees "blocks," it has to disambiguate from city blocks, writer's block, blockchain, blocking in theater...
HOW TO DO IT IN 20 MINUTES
1. Open Claude → Settings → Profile (or your Project's memory if using Projects)
2. Write your legend in slot 1 (copy the symbol set above or make your own)
3. Have Clause compress his 30 item memory about your work/projects/preferences into symbolic notation, pack 3-5 per slot and add lots more to improve recall and context
That's it. You now have 4-5× more persistent context, cleaner activation patterns, and a system that points to deeper storage when it matters. Every conversation you have from here forward starts smarter.
I open-sourced it. Templates, scripts, setup guide, the whole architecture.
https://t.co/VVFUNSOrlY
If you're building anything sustained with Claude — a product, a business, a long-term project — this might save you from explaining yourself for the hundredth time.
I gave Claude a hippocampus.
Every Claude session starts cold — you re-explain who you are, what you're building, what you decided last time.
I got tired of it. So I built a three-tier persistent memory architecture using tools that already exist.
It's called Hippoclaudus. Here's how it works:
Requirements:
- Claude Pro or Team (for MCP support)
- Python 3.10+
- mcp-memory-service package
- ~30 minutes to set up
No external services. Everything runs locally.