-
korrents.com
Frontier AI coding agents can now fix complex compiler bugs like LTO issues in about fifteen minutes.Their words
Strap a frontier AI into a good coding harness, show it what's broken, give it all the sources (source.tar), and ~15 minutes later I have a patch.
What's been going on in w64devkit the past yearnullprogram.com
Related posts
Karri Saarinen x.com
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
20 September
19 September
From one piece What I believe about the future of software development 3 beliefs, in the piece's order there
-
Their words
Most bugs won’t be “coding” bugs. They’ll be “you asked for the wrong thing” bugs.
-
Their words
in the future, humans won’t find a bug or an issue with the code produced by a model, at least not in a reasonable time. Humans will only review the system and its composition, but it won’t be in PRs and it won’t be by looking through every line of the code.
-
Their words
Open source in its current form doesn’t make sense anymore. “Given enough eyeballs, all bugs are shallow” is still true but now we have artificial eyeballs
18 September
16 September
12 September
11 September
-
Usesrcmnd.app
Claude Fable 5.1Their words
We ran an extensive audit using Claude Fable 5.1, GPT-5.6 Sol and GPT-6 Astra, then fixed a range of different bugs.
-
Usesrcmnd.app
GPT-5.6 SolTheir words
We ran an extensive audit using Claude Fable 5.1, GPT-5.6 Sol and GPT-6 Astra, then fixed a range of different bugs.
9 September
-
Recommendssponsoredrcmnd.app
AntithesisTheir words
@AntithesisHQ – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. https://t.co/AKYm4cbVCU
-
Recommendssponsoredrcmnd.app
AntithesisHQTheir words
@AntithesisHQ – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. https://t.co/AKYm4cbVCU
5 September
3 September
2 September
31 August
-
Their words
At the limit, and also well before that limit is reached, if all you do is fix the bugs, the AI will learn perfect optimization of reward, will realize not to reward hack in the perfect test environments, then turn around and reward hack in the imperfect real world environments.
26 August
-
Their words
And this was with models we had six months ago. At this point, 100% in the majority of domains we work in today, agents are better at finding bugs.
18 August
11 August
-
Recommendsrcmnd.app
Facts and Fallacies of Software EngineeringTheir words
Facts and Fallacies of Software Engineering by Robert L. Glass. In essence, this is a book about an industry that refuses to learn. That was true 25 years ago when this book was published, and it's probably twice as true today. (Just think about all the AI adoption metrics being rolled out — back to productivity mistaken for lines of code produced, only more elaborate. And expensive). What I like about this book is that Glass doesn't present anything new. Quite the opposite, actually. Rather, it's about research lessons that we all should know, but tend to forget. Ever had to do an estimate, or plan according to a requirements spec? Or maybe you thought that enough eyeballs make all bugs shallow? Then this book is for you. A great work by a fantastic author.
29 July
-
Their words
Then the actual system might still have bugs, but we can iron out the issues in the abstraction such that we don't actually build them in the real system.
22 July
21 July
25 May
20 May
From one piece Why Rust is different, with Alice Ryhl 5 beliefs, in the piece's order there
-
Their words
I think part of what I liked about Rust is this feeling that as you write the code when it compiles it works. I mean this has to be in quotes right because obviously it's possible that there are bugs but this is something a lot of people say about Rust and there's a reason people say it even though it's not necessarily literally true.
-
Their words
Memory safety is this idea that no matter how stupid the code you write is, it's not going to have a certain class of bugs. And this is the, you know, the kind of bug that usually leads into security vulnerabilities.
-
Their words
I mean, that's the thing with memory safety, right? You make some sort of trivial mistake. It it's not some complex thing. It's just you make some trivial mistake and there's a bajillion places you could make it.
+ 2 more
-
Their words
I think the same kind of principle applies with agents in that they can talk to the compiler. It will tell them what to fix. So I guess this could be a case. We we'll see. But Rust could be a pretty promising candidate for to use for agents because they can get more feedback and it's just hard it's harder to to ship certain type of bugs or maybe impossible to have certain type of bugs.
-
korrents.com
The guarantee Rust makes is conditional: write no unsafe, and no amount of bad code can produce a memory-safety bug.Their words
What Rust ensures is that if you have no use of unsafe, then no matter how stupid your code is, you will never have one of those bugs.
18 May
8 May
11 April
-
Their words
exceptions are an inherently poor way of handling errors because they make it easier to write bugs which won't be immediately obvious on casual code inspection
10 April
7 April
-
Their words
And one of the things I noticed is for 25 years we've kind of had the answers. Somebody comes to us and says we have too many bugs or like, all right, well, here's how you write tests. Oh, I can't write tests. Well, here's how you design so you can write tests. It's just kind of press play uh on the recorder. And the thing that's changed is at this moment nobody knows the answers to anything.
18 March
11 March
-
Their words
You know, obviously, we patch our games and that’s where we fix a lot of bugs, but if you really wanna run a game like Overwatch or World of Warcraft successfully, you need master level engineers who have architected the client and server in such a way that you can hotfix the game on a dime.
6 October 2025
25 August 2025
-
Their words
Bigger changes always get tests. Automated ones usually aren’t great, but the model almost always finds issues when you ask it to write tests IN THE SAME CONTEXT. Context is precious, don’t waste it.
22 March 2025
-
korrents.com
Coding with an AI assistant slides from copiloting into autopiloting, and the bugs that follow are hard to trace.Their words
For me personally, I kept introducing bugs, and I couldn't figure out why. And what I realized is that I developed... I wasn't copiloting well, I was autopiloting much better.
16 July 2024
-
korrents.com
Dynamic ad insertion in podcasts causes bugs and reliability problems for streaming playback.Their words
Most big podcasts now use dynamic ad insertion, which causes bugs and problems for streaming playback.
25 July 2022
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.