A lot of companies are already doing this. You need really good review agents, make sure it still goes through agentic review for very critical parts of your codebase and have co-workers that are good at assessing risks, and also owning it/fixing it in case things break.
In most of the world there is: no real willingness to solve problems nor an acceptance of people offering to solve their problems (out of pride) simply too much regulation so the problem cannot be solved without a license or long approval time very low standards of what is deemed acceptable so the problem isn't seen as a problem in the first place
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.
The safety guardrails in a way make it more dangerous not less I think because after rejecting you it becomes kind of a pedantic child that will just reject whatever If in that moment your server will go down and it feels it's related it could just reject fixing it
We tried this. We built a lights off software factory in July of 2025 and by November we had shut it down. I think it takes about three to six months of you shipping all the time with nobody reading the code before you realize like, wow, this is getting way worse and it's easier to start over than it is to fix it.
And uh it's still worth it's still worth not reading the code for most of the time at the cost of every once in a while I'm going to have to spend two weeks fixing an issue by hand. And I don't believe that anymore because I think the amount of code we're able to write now is actually like 10xed or 100xed and I think the problem's just getting worse.
I would prioritize trying to index, but just given how fast AI could, you know, hit the world. But, um I definitely wouldn't just rely on that because like it could the the sort of um messy middle type cases or the just a long timelines cases on which like you we don't get it anything like AGI all that soon.
I think this is kind of leads to another way that Rust really helps with reliability, which is that if you're refactoring, I think Rust is really good at telling you all the places you need to update. I've done this sometimes where I would refactor something. I change the code. I change the return type or whatever it is, and then I just fix the compiler errors and until the compiler stops shouting. And then once I've done that, I've updated every place I need to update.
there's a there's a series of of questions that I ask to to diagnose why is growth slowing in this order because it's one of these things where the first one that's a problem, if you don't fix that, it doesn't matter if you fix one of the ones below.
ultimately I think what matters is the use of AI in their economy to create economic value right I mean that's the uh the diffusion theory which is ultimately it's not the leading sector but it's the ability to use the leading technology to create your own comparative advantage right so that I think will fundamentally be the core driver
When AWS ships a service which is half-baked, it diminishes customer trust in AWS as a whole; even if the problems in that service ultimately get corrected (either by fixing them or in some cases by simply getting rid of a service which should never have existed in the first place) the memory of a failed launch will live on in customers' minds for years to come.
But for a variety of reasons I think it makes more sense to stay agnostic about forecasts of potential GDP growth, and focus more on the signals the current performance of the economy is sending.
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.