Related posts
Eugene Yan x.com
Stronger models have made finding vulnerabilities easier, and the bottleneck has shifted to verification, triage, patching. Here are some lessons from working with security teams to address the new bottlenecks.
The the words it uses that this site has seen least often elsewhere. Posts are matched on those words alone — nothing here is a summary of this one.
Top people
Showing Profile →
Hiding
Hiding
14 September
3 September
1 September
31 August
13 August
11 August
-
Their words
when AIs are extremely extremely capable my view is that those AIs will be harder to align than current systems. So for current systems, we have this feedback loop where we basically like we create an AI. We do some evaluations on it. We see that it has some kind of messed up behavior that we can kind of quickly understand. Then we like can like go look in training and be like, "Oh, the these training environments led to this problematic behavior. Let's like tweak that training data. Let's introduce some additional training data to like correct this other issue and then move forward from there." But in a regime where the AIs are extremely situationally aware, very very very very capable and um you know uh we don't necessarily understand what they're doing, this feedback loop breaks down.
12 July
-
Their words
The primary axis is no longer the politico-economic axis of capitalism-vs-communism, but the ethno-cultural axis of ethnomasochism-vs-ethnonationalism.
3 May
-
Their words
The bottleneck has shifted from doing the work to writing clear specs and reviewing outputs fast enough to keep the pipeline moving-the middle is hollowing out.
15 April
-
Their words
And so none of that my point is that none of the bottlenecks last longer than a couple 2 three years. None of them.
7 April
-
Their words
the point is that where we always get bottlenecked is where the the previous processes and and and heuristics don't apply. Right? Like that's almost sort of definitionally what causes the bottlenecks.
22 March
-
korrents.com
AI did not create the bottlenecks in software delivery; it threw gas on processes everybody already knew were weak.Their words
There were a handful of people probably managing a security review process or a launch process or a deployment process or, you know, sometimes reviews were a little slow and they got backed up. Well, now we just threw gas on the fire and so all of that is a problem.
13 March
-
Their words
So to scale compute further right there's some different bottlenecks this year next year uh but ultimately by 2829 the bottleneck falls to the lowest rung on the supply chain which is ASML right ASML makes the world's most complicated machine i.e. an EUV tool.
28 February
-
Their words
Even if AI can help design more effective drugs, timelines will not compress until we solve the operational and regulatory bottlenecks of trials.
23 January
20 December 2025
6 August 2025
Nothing matches.
What is a korrent?
A korrent is a belief a person has stated in their own words: one sentence stating the claim, backed by a quote and a source, kept at korrents.com.
Under a name here, the quoted block is what they actually said. The korrent beneath it is the claim those words support, in korrents' wording — tap it to see the record, its source, and who else holds it.
Nobody here wrote their own korrents. They are compiled from public statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they do, this site shows a machine translation beneath the post, in this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the serif above is exactly what the person published, and it is what to quote them on. A translation can be wrong in ways that matter, especially about tone.
Only the post's own words are translated. A quoted post, a linked article and a belief on korrents.com are left in their original language.