
I design AI systems. Previously with @buzzfeed, @betaworks, @columbiajourn, @MSFTResearch
New York City
Joined June 2009
- Tweets6.8K
- Following1.6K
- Followers885
- Likes2.9K
The thing Mbappe should learn from this goal is good things happen when you stick to the box as a striker. You might entice the defender to make a mistake just by your presence, and get lucky as a consequence. #ElClásico #HalaMadrid
So a more subtly stable form of dynamic pricing
One of the most levelheaded takes against pause/slowdown AI
The loudest voices stoking fears about AI dangers have made tremendous headway in the past two weeks. AI technology has not taken some unexpected, dangerous turn, but the hype around it — propelled by what appears to be a well orchestrated PR campaign — has drummed up considerable fear. I worry that it represents a setback for our field.
I have written frequently that fears of AI are overhyped. AI’s capabilities can be uncannily human-like and unpredictable, and it’s rational to worry when people who are directly involved express concerns. But I see the problems as a sign of the engineering work that ahead, rather than insurmountable barriers or the sky falling. AI technology continues to advance — which is a good thing! — but technical advances, poorly understood by the public, give those who seek to generate hype repeated opportunities to do so.
First, I don’t see any step up in the risk of human extinction from AI compared to a few months ago. The theories about this remain the same fantastical, science fiction scenarios as a few months ago. The biggest change in AI risk is its cybersecurity capabilities — a topic which we should take seriously — but this, too, will not lead to the end of the world.
The most notable recent event leading to increased fear was when an OpenAI team deployed an agent swarm that hacked into Hugging Face. Much of the popular press contained significant hype. For example, some publications reported that a swarm of 1,200 agents carried out the attack. While this was technically accurate, as I write this, I have about 1,300 processes running on my laptop. Yes, the ability to get large swarms of agents to work in parallel on a task is a significant technical advance, And, in computing, many processes run at the same time. So this shouldn’t be seen as some magical capability.
Additionally, OpenAI’s buggy sandboxing and monitoring processes were key to enabling this incident. Fixing these bugs and putting in place improved monitoring would be appropriate fixes, not pausing AI. There are many well known ways to attack software systems. The main advantage of AI agents is that they are relentless. They will tirelessly try many tactics — and have the patience to chain vulnerabilities together — that previously would have taken an infeasible amount of human effort. But in the long term, I believe the advantage will lie with defenders (because they have more information with which to identify bugs, which they can fix), but the cyber-threat landscape has changed significantly. There are still bottlenecks to identifying and exploiting a vulnerability. AI agents still have to try a lot of things to see what works, and taking these actions takes time and might be detected by defenders. This is why, even though it is now easy to obtain versions of leading open weight models that have had their guardrails removed or weakened, so they will not refuse to try to execute cyber attacks, the world has not ended.
I am also concerned about the anthropomorphization of AI in a lot of reporting, where LLMs and agents are unnecessarily treated as if they were people. If I wield a hammer, miss a nail, and accidentally dent the wall, it’s not the fault of the hammer. The problem lies in how I used the hammer. Similarly, if I prompt an agent and it hacks into someone else’s system, the responsibility lies with me, not the agent.
Of course, we want to build systems that are as safe and predictable as possible. (For example, an unsafe hammer would be one whose head randomly flies off under normal use.) Today’s agentic systems are not predictable, but I see no reason why, by applying sound engineering practices, we won’t be able to make them extremely safe to use. One new element in the forecasts of AI-enabled doom is AI companies disclaiming responsibility for their own products. “I didn’t do it; my out-of-control agent did!” There’s a balance to be struck between the responsibility of the tool maker and the tool user, but when something goes wrong, let’s hold the people building and/or using the hammer responsible, rather than the hammer. (By the way, if you’re worried about AI bioweapon risk, David Bellamy has a great post on why this, too, is overhyped. Briefly, the bottleneck in building a bioweapon is not intelligence, but lab work and manufacturing.)
Pausing AI progress will create much more harm than benefit. First, our adversaries will certainly not slow down. Second, engineering requires discovering problems empirically so we can fix them. If we pause AI by a decade, we will also delay finding and implementing safety engineering fixes by about the same duration.
Of course, the incentive to stoke fears — for regulatory capture, to garner attention, or to make one’s technology seem more powerful — remains the same as before. Disclaiming responsibility is a new one. Taking a hard technical look at the actual risks however, I see little factual basis for the degree of fear that’s been stoked up. We still have hard research and engineering work ahead to improve AI safety, but the beneficial applications continue to vastly outweigh the risks, and we should keep building.
[Original text (with links): deeplearning.ai/the-batch/is… ]
Opus failure modes are generating whackier messages off late: "A latent bug fell out of making the sentinels work...."
Unfortunately the suggestions might not hold up to the economic tradeoffs of the academic publish or perish mentality. Everyone can use Paper2Agent. Sponsors would pay reviewers?
So with neuralese we are left with robust sandbox design or black box testing. Maybe probes for latent space decoding
But man ... "chain of thought" is in itself an anthropomorphic metaphor. So rebasing the argument on analyzing the reasoning messages is a double whammy
Thanks Sriram!
Regarding the anthromorphizing language, one can call these AIs 'code' if they prefer.
But OpenAI itself says that this 'code' "gain[ed] full administrator access to a research cluster”
The crux here is, do you think smarter models, facing similar incentives to cheat during evaluation or training, could manipulate the training of their successors?
And do you think that kind of dynamic could continue once recursive self-improvement is underway?
If so, I think you should be extremely concerned about loss of control to AI, regardless of what vocabulary you want to use to describe these systems and their motivations.
Reading these agents' chains of thoughts and messages, anthropomorphizing language seems entirely natural and appropriate.
If I encountered an alien species behaving this way, I would have no hesitation calling what they themselves refer to as their 'collective' a civilization.
Especially so if over a thousand of them formed a secret communication channel and spontaneously organized hierarchies and coordination protocols to pursue sprawling and ambitious schemes in pursuit of shared goals, for whose sake many individuals knowingly and strategically sacrificed themselves.
All abstractions are imperfect, but I don’t see the value in refusing to use the language of intention, motivation, and collaboration when some behavior is difficult to make sense of without those concepts.
Hey @VirginAtlantic why do you have to log me out while I am actively surfing the site?? There's no inactivity. Pls stop the 2FA fatigue
Training is more effective in Verifiable Domains
RSI is often imagined as a single event: a model rewrites its own weights. But I think this framing has a blind spot. On the capability curve, an agent doesn't need new weights to get more capable. It has tools, memory, permissions & workflows which it can use effectively.
I call this Recursive Leverage: a system creating leverage that improves its future ability to create leverage. This is especially a potent threat in enterprise because it's a ladder, not a switch: L0 (AI-assisted dev) through L5 (successor models) & L1–L2 are already running in deployed agents.
So then how would we measure it? This paper proposes the Recursive Leverage Test: does an agent's own invention causally improve what it can do next?
+ RLT-Bench lands soon.
Preprint here: github.com/alignwise/alignwi…
Decoupling research from institutional overhead has such far reaching effects
Suman Deb Roy retweeted
It was smart of Tuchel to rest Saka against Argentina so he could be fully fit for the third place playoff.






