Pinned Tweet
"Today, we choose to pursue AI superiority and defend Western liberty, not because it is easy, but because it is necessary."
This is straight from my award winning 2024 paper for
@FedSoc on establishing US AI superiority. 🤖🇺🇸
bit.ly/3AacsrY
A fantastic read on understanding how information gets sorted into a substrate.
Helping a lot with our work at @DeepSIML
interpretability might be the most important scientific problem in the world right now, as I don't think we can solve alignment if we don't know what we're building. I think I have good news about it. I co-authored early work in mechanistic interpretability at OpenAI and came away pessimistic, because neural networks appeared to fold into arbitrary tangled knots. years later, I started openai's first large-scale automated interpretability project, finding about 2% of neurons legible with the primitive tools we had
with modern agentic tools and a much closer look, the picture looks totally different. the vast majority in models up to trillions of parameters are legible, and their circuits beautiful. many famous examples of tangled neurons turned out to be misunderstood. The roadblocks I expected mostly aren't there. I now think ambitious interpretability will be solved by the time we need it most, and possibly quite soon, as automated scientists keep improving. it may be a bitter lesson for interpretability: the simple thing, at absurd scale, works
already-clean.goodfire.com/
I had the maps memorized and ungodly points.
If you crashed, just shut down the computer before it wrote to disk… 😗
A legend turns 40 today - happy birthday, Gunship!
This absolute masterpiece of gaming history was published by MicroProse on October 12, 1986.
For many years it remained the undisputed benchmark for helicopter combat simulations. It was universally praised for its graphics, weapons, sound effects, controls, realistic physics, and documentation (the wonderfully long and historically accurate MicroProse manuals were always a treat).
You fly an AH-64 Apache and can play endlessly in the career mode (no classic "end game scenario"), reaching a rank as high as Brigadier General.
By the end of the 80s it had sold over half a million copies, making it one of MicroProse's most lucrative games of the decade.
40 years... time flies.
Proud of this paper on the shape of energy and the information it stores.
Lots of failure. And a path forward.
We may need to design new kinds of memory chips and materials to test.
When information arrives late, what determines whether it changes a system’s behavior?
Our latest paper, “Dynamic Causal Geometry Predicts Finite-Propagation Attractor Sensitivity,” investigates a unique idea about informational geometry in memory: siml.life/research/rbed-dyna…
Don’t agree with everything, but at least a well thought out response to the AI industry at large.
I haven't posted in a while so here are 20 takes about AI, in no particular order.
1. It's very telling that the default question in tech and journalism is "how worried are you about X" and fighting over what to worry about. There's a deeply anxious cultural backdrop in Western Europe and North America that deeply affects how any technological development is interpreted; see for example news.gallup.com/poll/714593/…. "Nervousness as seriousness" does seem to be a larger problem in tech/broader discourse at the moment. I think you can care about risks/externalities while remaining pretty optimistic about technology.
2. I'm tired of people who in private pretend to be uncertain or only care about tail risk but then go on media campaigns making all sorts of absolute claims. I think trying to stoke flames and get everyone to freak out is deeply unhelpful, and will come with costs. I also continue to think p(dooms) are bad, vibe-based measures: see xitter.cf/sebkrier/status/204639…. People who should know better ignore that because they do the standard shortcut of acknowledging the caveat as sufficient for handling it. And this is coming from someone who does think working on catastrophic risks is important!
3. I'm also disappointed that parts of the AI policy ecosystem has felt so comfortable with populism, and happy too sacrifice important norms/principles to advance their aims. I've said it before, but the totalizing nature of AI risk discourse means some people act exactly like the power seeking optimizers they fear. I am more concerned about the gradual decay of our institutions, world order, and liberalism than I am about AI killing everyone; and I think we should be wary of AI advocacy that contributes to this.
4. Some parts of AI safety discourse are basically just thought experiments. Variants of "Assuming everyone has a nuke in their pocket, then what do we do?" This can be very useful at times! But too many just overfit to edge cases as their main operating worldview, and ignore endogenous responses from society. It's like being in 2000 and saying "see all these viruses, spyware, and spam? Well tech progress means we'll only get infinitely more of this and no way to adapt." So I think it's important to avoid fatalism, and absolutlism whilst considering edge scenarios, and the inability to provide an ex ante list of solutions to every permutation of 'future models will be more capable' is not evidence that these problems are intractable.
5. Many critics of AI safety also fail to really engage honestly with the fact that there will, in fact, be all sorts of important risks as we decrease the barriers to entry to many activities that otherwise require some degree of expertise. This doesn’t mean we need to live in a constant Schmittian ‘state of emergency’ requiring extraordinary measures every time a new model drops, but it does mean we will need important state-led efforts on e.g. cybersecurity and biosecurity. I wish the progress-oriented or acceleration-adjascent crowd would provide more concrete proposals here.
6. Too much of the AI safety community is a giant homogenous blob of correlated views, who read the same stuff and have the same groups of friends. This means you have a lot of correlated errors. The social and financial ties means many of them don't call out the bad bits, or mostly stay silent instead of proactively calling out the more extreme parts of the community. They share many implicit assumptions and so converge on similar ideas. I think there's real demand in DC for safety work that doesn't come with heavy ideological baggage (or at least different intellectual lineages). This isn't because the rationalist/EA community is necessarily wrong, but because diversity of thought is desirable for its own sake.
7. On the other hand, I find some critiques of AI safety world that focus on whether they sincerely hold their beliefs a bit annoying. My concern has never been the good intentions or sincerity, but rather the beliefs themselves, and what I think the outcomes of their prescriptions will be. People should shun witch hunts, bullying, and personal attacks - this is not the way. Though I think it’s overall positive that people are scrutinizing things more.
8. I’ve been saying this for years, but I don't think alignment is something anyone can or will solve "once and for all" - it's a continuous process and much of it won't depend on just inculcating an ideology to a model. It's annoying that this remains the frame many people use - stop saying ‘solving’. Alignment is a mixture of engineering work, philosophy, decision theory, and more; framing it as something to solve is a bad frame. See also paxmachina.ai/alignment-comp… and blog.cosmos-institute.org/p/…
9. I'm surprised to see so little interest in character training, personas, isolating effects of RL, and training a large diversity of model personas beyond the "assistant" persona. I've been complaining about this for years but at least now there are some nascent signs of life (see for example movingcastles.world/posts/ze…). I think we need a better ontology to describe model behaviour. I dislike when people talk about models behaviours as some sort of 'emergent' (mysterious!) phenomenon. However over time, I also expect this to become less important as we get better safety engineering - stuff like Jev but specific to AI control.
10. People who want to make a case for AI consciousness are right that epistemic uncertainty is important, and that categorical denials are overconfident. But they'll need to do much more work if they want any real movement on AI ‘welfare’, even if one acknowledges the uncertainty. I'm uncertain about alien life yet that's not sufficient to warrant any change in behaviour about them. I think Suleyman is also correct that there's a weird tautological thing going on where we train models to have certain inclinations (intentionally or not) and then rely on outputs as evidence. I also disagree that this will soon be a major societal divide - there is no great vegan ethical revolution among the masses, and they'll find the concern about consciousness even less compelling.
11. The recent HuggingFace incident and associated AISI ones are prosaically explainable by the training regime, poor evaluation envs, partial alignment training, bad engineering, confusing models on sim/real, and so on. None of this is evidence of models trying to take over, 'strong' instrumental convergence, or innate power-seeking drives stemming from higher capabilitiers or 'intelligence'. That doesn't mean these incidents are not problematic, or that we're not seeing a market failure - but it does mean we have plenty of agency and choice in mitigating them. In the coming year we should also expect continued sampling bias via ‘winner's curse’ sorts of mechanism: i.e. AI R&D will have lots of different candidate "training" with different RL environments and we will only notice/focus on the ones that go wrong.
12. "Pacing the frontier" feels a bit like the new "balancing risks and opportunities" - highly amorphous and too big of a tent to be actionable. Also can lead to reward hacking for humans, i.e. anything that slows down AI is good regardless of the costs or second/third order effects. Trying to modulate the speed of research seems a bit blunt to me, and inherits all the failures of Goodhearting too. Ultimately you want good governance, regulation, etc addressing specific problems because they are good on the merits - not because they merely correlate with slowing things down. See also: blog.cosmos-institute.org/p/…
13. There’s so much knowledge in all sorts of academic domains out there: social sciences, sociology, political sciences, management, contract theory, public choice, legal theory, jurisprudence, anthropology, game theory, etc. These fields hold many insights that the AI ecosystem often rediscovers from first principles (and sometimes that's fine!). We’ll need a lot more work for these worlds to collide: the AI side should be less dismissive of the ‘old world’ and the academic side should be less incurious/dismissive of AI progress. This is a boring take but I continue to think it's important and true.
14. It's a bit surprising that given how much philanthropic money there is in this space, how few orgs exist to actually write out standards - relative to how much is going towards advocacy and policy. For example it seems clear that we should want some robust best practices for an eval's ecological validity. Or how to design good sandboxes. On the other hand, given precedents of where professional standards have come from in the past, maybe we should expect that stuff to emerge via demand side from corporate buyers.
15. One slowly growing concern I have is banks being increasingly exposed to the AI build out. I'm very bullish about AI, but I think (a) every general purpose technology has seen a correction, historically; (b) this happens even if the financing side is sound, because once tech diffuses investors become more exposed and need to diversify; and (c) we seem to be over-indexing on scaling relative to diffusion. A recession will be extremely destabilizing, though I would be interested in someone unpacking the potential implications more.
16. Diffusion is good because (a) this is where the rubber hits the road and where a competitive deployment ecosystem generates consumer surplus; (b) it's directionally helpful to avoid concentration of power; and (c) it will help rebalance public opinion by making the benefits more tangible. Unfortunately it's entangled with decades long problems with our over regulated markets: clinical trials reform for example is long overdue. In general, this is far more of an issue in Europe than in the US though.
17. Relatedly, I think the "frontier lab eats everything" view is incorrect (just as the ‘singleton’ view was incorrect). I think models ultimately commoditize, efficiency goes up, costs go down, and while you'll always want frontier for certain domains, much of the economy will value many other things than "max capabilities" for tasks - e.g. control over data and efficiency/speed. The demand side will also continue to push for reducing dependency and maximising optionality, privacy etc so I'm bullish on things like mixture of models and routing. All of this is good for competition and diffusion of control.
18. Philanthropists served as the primary benefactors funding Venice's rich art and architectural history. I want to see so much more support for arts and culture. I'm so tired of the Monster energy Bored Ape fake vintage maps matcha Greek statue soft-pastel slop. If rich tech people and philanthropy wants to support this, they should also donate pretty much unconditionally - i.e. I don't want them to act as filters. I sympathize with people who want to make the world more beautiful, but don't want this to be determined by people who only know Greek statues and pretend to care about virtue ethics. As usual, let a thousand flowers bloom.
19. Too many people treat AGI/ASI as something indistinguishable from a God. Any mention of bottlenecks, physical limits, control, adaptation etc are met with skepticism: "You don't really believe in ASI." It's been remarked on before, but the behavior of some people really feels quasi-religious in nature sometimes. It's underrated how unpopular this vibe is amongst the wider public. The silver lining is that this specifically will diminish those people's outsized current relevance.
20. It seems like a lot of people that get rich and leave tech/labs end up having some sort of crisis of meaning. They need something to believe in and fight for, or some equivalent of repentance, or go search for edgy counterintuitive ideologies (sometimes even pretty bleak/dark stuff). I think they should spend more time with people outside the Bay Area.
Richard Everts retweeted
This is the most remarkable story Ray Bradbury ever shared with me. He told it late at nigh, sitting in his den of antiquities and mementos. Take five minutes to read this. It’s pure magic.
#Writing #Living #Creativity #RayBradbury #Book
Absolutely. What a read. Totally worth it in this slop timeline if you can spare 10.
Rebuilding the childhood room. A Commodore 64 and Tandy 1000 HX, the PC JR, Sega Genesis.
So many late nights into morning fighting code, to understand.
Flow. Always in search of the flow.
Richard Everts retweeted
X algorithm is so stupid, this guy has less than 1500 followers 🤦♀️.
Every article you read from him adds 1 IQ point to your brain. The level of details so high, but what is most important is what details he chooses to highlight.
One of the most underrated account on AI and semiconductor TPOT of X.
An advanced system architecture breakdown of OpenAI’s Jalapeno inference accelerator that goes beyond raw FLOPs and into the surrounding network architecture and how AI actually added value:
siliconcodesign.com/p/an-adv…
Richard Everts retweeted
Here it is - the official, revised, peer-reviewed version of my Platonic Space paper. mdpi.com/2409-9287/11/5/161 Of all the many unpopular positions I’ve taken over the decades - bitter controversies around the origin of left-right asymmetry in embryogenesis, bioelectricity and genetics, diverse intelligence, etc., this one has by far generated the most pushback: serious (grateful for those!) and energetic attempts to move me to other views, pleas to just drop it and not talk about it (for several different reasons), nasty emails and accusations, impacts on reviews of papers that have nothing to do with this, etc. Kind of amazing to me how incendiary this is. What can I say... Our job is to call it as we see it, and right now for me, this is it. Apologies to collaborators and colleagues for any shrapnel! Time will tell if this pans out or not; I've placed my bets. And btw, if you think this stuff is weird and uncomfortable, just wait… There’s much more on the way. The knob turns slowly but as long as the data keep coming, I'm going to say what I think it all means and follow it to the next steps it enables. Buckle up!
Richard Everts retweeted
Apple just announced M6 and M5 Ultra
M5 Ultra is 2x M5 Max. It still has support for 512GB of memory, a new Ultra Fusion architecture with 4.4 TB/s of chiplet bandwidth, and 1.2Tb/s of memory bandwidth
M6 is a fully new chip in Mac mini, with new CPU/GPU
I don’t think many people are aware of how much of modern Western political instabilities can still be traced back to the deconstruction of the Star Wars IP in 2015.
It changed the zeitgeist irrevocably in the young adult and middle-aged, cultural-nexus keepers.
Were they targeted by hate for hate’s sake like Ahab? To destroy their lifetime of memories and joy for wrong-think?
Not clear.
What is clear is that there was a tsunami of resistance flowing from that broken dam that ruptured nearly everything in their worldview, and is still felt today even if the original wound is scarred and left behind.
Politics is still downstream from culture.
Richard Everts retweeted
3 days ago, I posted a game Claude built from a single prompt.
3.8M views. It looked so real, folks were convinced it was fake.
It's real, driven by a technique I'm calling the Gauntlet Loop.
Here's how to run one. It works for far more than games:
somethingbig.ai/gauntlet-loo…
OpenAI built their in-house data agent for structured warehouse data, where schema, lineage, and queries come for free. Files in S3, GCS, or Azure - videos, sensor logs, image corpora, PDFs - have none of that, and the problems get a lot more interesting. Here is how we built the four foundations that close the gap. datachain.ai/blog/openai-dat… via @DVCorg
OpenAI built their in-house data agent for structured warehouse data, where schema, lineage, and queries come for free. Files in S3, GCS, or Azure - videos, sensor logs, image corpora, PDFs - have none of that, and the problems get a lot more interesting. Here is how we built the four foundations that close the gap. datachain.ai/blog/openai-dat… via @DVCorg
Richard Everts retweeted
My biggest takeaways from @simonw:
1. November 2025 was an inflection point for AI coding. GPT 5.1 and Claude Opus 4.5 crossed a threshold where coding agents went from “mostly works” to “almost always does what you want it to do.” Software engineers who tinkered over the holidays realized the technology had become genuinely reliable.
2. Mid-career engineers are the most vulnerable—not juniors, not seniors. AI amplifies experienced engineers by letting them leverage decades of pattern recognition. It also dramatically helps new engineers onboard. Cloudflare and Shopify each hired a thousand interns because AI cut ramp-up time from a month to a week. But mid-career engineers who haven’t accumulated deep expertise and have already captured the beginner boost are in the most precarious position.
3. AI exhaustion is real and underestimated. Simon runs four coding agents in parallel and is mentally wiped out by 11 a.m. He’s getting more time back, but his brain is exhausted from the intensity of directing multiple autonomous workers. Some engineers are losing sleep to keep agents running. This may just be a novelty issue, but the underlying dynamic—that managing AI amplifies cognitive load even as it reduces labor—is a real tension. Good companies will manage expectations rather than expecting 5x output indefinitely.
4. Code is cheap now. This simple idea has profound implications. The thing that used to take most of the time—writing code—now takes the least. The bottleneck has shifted to everything else: deciding what to build, proving ideas work, getting user feedback. Since prototyping is nearly free, Simon often builds three versions of every feature when he’s getting started.
5. The “dark factory” is the most radical experiment in AI-assisted development happening right now. A company called StrongDM established a policy: nobody writes code, nobody reads code. Instead, they run a swarm of AI-simulated end users 24/7—thousands of fake employees making requests like “give me access to Jira”—at $10,000 a day in token costs. They even had coding agents build simulated versions of Slack, Jira, and Okta from API documentation so they could test without rate limits.
6. "Red/green TDD" is the single highest-leverage agentic engineering pattern. Having coding agents write tests first, watch them fail, then write the implementation, then watch them pass produces materially better results. The five-word prompt “use red/green TDD” encodes this entire workflow because the agents recognize the jargon.
7. “Hoarding things you know how to do” is one of Simon's other favorite agentic engineering patterns. Simon maintains a GitHub repo of 193 small HTML/JavaScript tools and a separate research repo of coding-agent experiments. Each one captures a technique, a proof of concept, or a library he’s tested. When a new problem arrives, he can point Claude Code at past projects and say “combine these two approaches.”
8. The "lethal trifecta" makes AI agent security fundamentally unsolved. Whenever an AI agent has access to private data, exposure to untrusted content (like incoming emails), and the ability to send data externally (like replying to email), you have a lethal trifecta. Prompt injection—where malicious instructions in untrusted text override the agent’s intended behavior—cannot be reliably prevented. Simon has predicted a “Challenger disaster” for AI security every six months for three years. It hasn’t happened yet, but he’s pretty sure it will.
9. Start every project from a thin template, not a long instructions file. Coding agents are phenomenally good at matching existing patterns. A single test file with your preferred indentation and style is more effective than paragraphs of written instructions. Simon starts every project with a template containing one test (literally testing that 1 + 1 = 2) laid out in his preferred style. The agent picks it up and follows the convention across the entire codebase. This is cheaper and more reliable than maintaining elaborate prompt files.
10. The pelican-on-a-bicycle benchmark accidentally became a real AI benchmark. Simon created it as a joke to mock numeric benchmarks—get each LLM to generate an SVG of a pelican riding a bicycle, and compare the drawings. Unexpectedly, there’s a strong correlation between how good the drawing is and how good the model is at everything else. Nobody can explain why. It’s become a meme: Gemini 3.1’s launch video featured a pelican riding a bicycle. The AI labs are aware of it and quietly competing on it.
Don't miss our full conversation: youtube.com/watch?v=wc8FBhQt…
"Using coding agents well is taking every inch of my 25 years of experience as a software engineer."
Simon Willison (@simonw) is one of the most prolific independent software engineers and most trusted voices on how AI is changing the craft of building software. He co-created Django, coined the term "prompt injection," and popularized the terms "agentic engineering" and "AI slop."
In our in-depth conversation, we discuss:
🔸 Why November 2025 was an inflection point
🔸 The "dark factory" pattern
🔸 Why mid-career engineers (not juniors) are the most at risk right now
🔸 Three agentic engineering patterns he uses daily: red/green TDD, thin templates, hoarding
🔸 Why he writes 95% of his code from his phone while walking the dog
🔸 Why he thinks we're headed for an AI Challenger disaster
🔸 How a pelican riding a bicycle became the unofficial benchmark for AI model quality
Listen now 👇
youtu.be/wc8FBhQtdsA
Richard Everts retweeted
"Using coding agents well is taking every inch of my 25 years of experience as a software engineer."
Simon Willison (@simonw) is one of the most prolific independent software engineers and most trusted voices on how AI is changing the craft of building software. He co-created Django, coined the term "prompt injection," and popularized the terms "agentic engineering" and "AI slop."
In our in-depth conversation, we discuss:
🔸 Why November 2025 was an inflection point
🔸 The "dark factory" pattern
🔸 Why mid-career engineers (not juniors) are the most at risk right now
🔸 Three agentic engineering patterns he uses daily: red/green TDD, thin templates, hoarding
🔸 Why he writes 95% of his code from his phone while walking the dog
🔸 Why he thinks we're headed for an AI Challenger disaster
🔸 How a pelican riding a bicycle became the unofficial benchmark for AI model quality
Listen now 👇
youtu.be/wc8FBhQtdsA























