-
Their words
The feedback loops that drive system change are both "highly destabilizing and difficult to predict."
Related posts
Addy Osmani Blog
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
18 September
14 September
8 September
-
korrents.com
Agent skills are now a valuable form of software.Their words
Skills are now a valuable form of software, like Emil's world-class design eng work. Projects like 𝚙𝚐𝚋𝚘𝚝, 𝚔𝚗𝚒𝚙, 𝚞𝚗𝚕𝚒𝚐𝚑𝚝𝚑𝚘𝚞𝚜𝚎 create amazing AI engineering loops.
6 September
3 September
1 September
28 August
26 August
-
korrents.com
The feedback loops a person allows to operate on them shape who they become to an unsettling degree.Their words
The lesson is that the feedback loops that we let work on ourselves shape us to an unsettling degree.
25 August
19 August
-
korrents.com
Letting automated loops build everything without guardrails on blast radius and on quality is a recipe for disaster.Their words
But, simply just having your loops build everything without having some guardrails around the blast radius without having guardrails around how you think about quality, I think is a recipe for disaster.
10 August
-
Their words
So if you design call it loop, call it graph, call it workflow, it's kind of all the same. If you design something that gets a trigger or gets an input and does something for you and maybe there's a decision in the way, boom, there's your graph.
7 August
-
korrents.com
Solving a systemic problem by doubling down on the same approach risks creating uncontrollable feedback loops.Their words
As a general matter, trying to solve a systemic problem by doubling down risks creating out-of-control feedback loops.
30 July
-
Their words
And I think there's a lot of room in a lot of domains for much faster validation models, possibly learned valu validation models that can uh you know get you a a approximation to the true answer much much more rapidly. And that changes how those experimental loops can be thought of and how quickly you can go around those loops.
20 July
15 July
From one piece Context engineering with Dex Horthy 4 beliefs, in the piece's order there
-
Their words
if you want to do loops engineering, you should build one loop at a time and you should keep them small and contained. Basically, I think everything except stop reading the code is really good advice.
-
Their words
And I think the lesson in loops engineering is like if you can make a problem very verifiable, you can kind of like treat it like a black box
-
Their words
You'll notice what I said was not use loops to ship the features that users want. We use loops to actually improve the codebase quality and we read all the code because we care about how it's architected and we care not just about the system architecture but what I would call the program design
+ 1 more
-
Their words
So I think the the thing I'm most excited is actually like what we call like iterated loops or like slow loops where we basically have a cron job. We have the loop the the the structure of the loop is really easy. It's like run this llinter fix one thing commit and push and then we run that every night in our GitHub actions and we wake up every morning to one PR that makes the codebase a little bit better.
14 July
24 June
-
Their words
I think a lot of the things that people might say that like oh, it was a waste of time to learn this subject cuz I didn't actually use like those details on the job. I think that's a very wrong way to think about it. And I think that's what a lot of people are doing now with AI. Like hey, what what if I'm not going to be writing for a loops a couple years from now. Um I don't think those things are a waste of time.
16 June
3 June
-
Their words
we went from infrastructure is code to infrastructure is data and infrastructure is code is like if this do that um bring in this module for loops all this stuff and Kubernetes is like no no no you have to specify exactly the containers you want how much memory that they need and then we have the status field to tell you if they were running or not
21 May
22 March
-
Their words
Well, now I'm getting feedback so quickly that I'm having to sometimes rebuild my mental model dozens of times in like a 30-minute period.
11 September 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.