Tap a claim on the ring to put it at the centre.
← A team that slows down and reads every pull request and every line of…
17 connected korrents · 16 moments from 25 Apr 2025 to 23 Sept 2026.
Everything filed under coding agents
coding agents
Everything filed under software quality
software quality
Everything filed under LLMs
LLMs
Everything filed under AI agents
AI agents
Everything filed under product management
product management
Everything filed under LLMs
LLMs
Everything filed under data centers
data centers Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Read this korrent: A team that slows down and reads every pull request and every line of code should expect only a 30 to 50 percent productivity lift from AI. A team that slows down and reads every pull request and every line of code should expect only a 30 to 50 percent productivity lift from AI. Last stated 3 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — tap for who they are
Same subject: The absence of a visible productivity jump from AI proves nothing, because a real ten percent uplift across the board would be impressive and almost invisible from outside. — tap to centre the map on it The absence of a visible productivity jump from AI proves nothing, because a real ten percent uplift across the board would be impressive and almost invisible from outside. Last stated 2 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: Having the very best AI model and harness does not result in better or faster execution and can slow teams down — tap to centre the map on it Having the very best AI model and harness does not result in better or faster execution and can slow teams down Last stated a month ago
19 Sept 2026
GO
Gergely Orosz — holds since 2026-09-19 — tap for who they are
Same subject: The very large productivity gains from agents require working with them directly; putting another human in between is too slow to preserve the gain. — tap to centre the map on it The very large productivity gains from agents require working with them directly; putting another human in between is too slow to preserve the gain. Last stated 2 months ago
26 Aug 2026
DH
David Heinemeier Hansson — holds since 2026-08-26 — tap for who they are
Same subject: Delivery will keep being slow until companies apply AI to the human, business-process half of it, not just to coding. — tap to centre the map on it Delivery will keep being slow until companies apply AI to the human, business-process half of it, not just to coding. Last stated 7 months ago
22 Mar 2026
NF
Nicole Forsgren — holds since 2026-03-22 — tap for who they are
Same subject: An AI coding factory combined with an old-style roadmap probably leads teams into the backlog, parity and churn traps at machine speed. — tap to centre the map on it An AI coding factory combined with an old-style roadmap probably leads teams into the backlog, parity and churn traps at machine speed. Last stated a month ago
10 Sept 2026
CV
Claire Vo — holds since 2026-09-10 — tap for who they are
Same subject: The AI research cycle from idea to experiment will likely soon be 10x faster, but that may not make researchers 10x more productive in the field's net understanding. — tap to centre the map on it The AI research cycle from idea to experiment will likely soon be 10x faster, but that may not make researchers 10x more productive in the field's net understanding. Last stated a month ago
22 Sept 2026
NL
Nathan Lambert — holds since 2026-09-22 — tap for who they are
Same subject: AI has already made sweeping mechanical changes cheap; the unsolved problem is getting the same productivity when adding features to an old, entangled codebase. — tap to centre the map on it AI has already made sweeping mechanical changes cheap; the unsolved problem is getting the same productivity when adding features to an old, entangled codebase. Last stated 7 months ago
1 Apr 2026
TP
Thuan Pham — holds since 2026-04-01 — tap for who they are
Same subject: The massive AI build-out is the right thing to be doing, and the only thing that will slow it is supply. — tap to centre the map on it The massive AI build-out is the right thing to be doing, and the only thing that will slow it is supply. Last stated 4 months ago
18 Jun 2026
LT
Lip-Bu Tan — holds since 2026-06-18 — tap for who they are
Same subject: 95 percent of the software made in an age of abundance will be shitty, and shitty software is easy to deal with because it goes away. — tap to centre the map on it 95 percent of the software made in an age of abundance will be shitty, and shitty software is easy to deal with because it goes away. Last stated 4 weeks ago
23 Sept 2026
GT
Geoff Teehan — holds since 2026-09-23 — tap for who they are
Same subject: A feature added to a codebase is extremely difficult to remove once other code is built on top of it. — tap to centre the map on it A feature added to a codebase is extremely difficult to remove once other code is built on top of it. Last stated 2 months ago
1 Sept 2026
VB
Vicki Boykis — holds since 2026-09-01 — tap for who they are
Same subject: A feature shipped in a product's official release is fair to judge, regardless of whether the company labels it a beta. — tap to centre the map on it A feature shipped in a product's official release is fair to judge, regardless of whether the company labels it a beta. Last stated a month ago
14 Sept 2026
JS
Jason Snell — holds since 2026-09-14 — tap for who they are
Same subject: CMake tooling is missing a linter that could statically catch most CMakeLists.txt mistakes. — tap to centre the map on it CMake tooling is missing a linter that could statically catch most CMakeLists.txt mistakes. Last stated a month ago
20 Sept 2026
CW
Chris Wellons — holds since 2026-09-20 — tap for who they are
Same subject: Comparing code coverage between passing and failing test runs is a cheap, effective way to localize a bug quickly. — tap to centre the map on it Comparing code coverage between passing and failing test runs is a cheap, effective way to localize a bug quickly. Last stated a year ago
25 Apr 2025
RC
Russ Cox — holds since 2025-04-25 — tap for who they are
Same subject: Everyone is rethinking code reviews, deploys, and possibly observability — tap to centre the map on it Everyone is rethinking code reviews, deploys, and possibly observability Last stated a month ago
16 Sept 2026
GO
Gergely Orosz — holds since 2026-09-16 — tap for who they are
Same subject: AI-assisted coding will generate a lot of low-quality output that developers will need to clean up, even as it also produces good results. — tap to centre the map on it AI-assisted coding will generate a lot of low-quality output that developers will need to clean up, even as it also produces good results. Last stated 8 months ago
9 Feb 2026
SH
Scott Hanselman — holds since 2026-02-09 — tap for who they are
Same subject: AI-generated code should be treated as untrusted until there is evidence it preserves the intended behavior. — tap to centre the map on it AI-generated code should be treated as untrusted until there is evidence it preserves the intended behavior. Last stated 2 months ago
19 Aug 2026
JS
Jon Seager — holds since 2026-08-19 — tap for who they are
Same subject: As AI makes it easier to generate code, teams must delete code more aggressively or be overwhelmed by accumulated complexity. — tap to centre the map on it As AI makes it easier to generate code, teams must delete code more aggressively or be overwhelmed by accumulated complexity. Last stated 2 months ago
1 Sept 2026
VB
Vicki Boykis — holds since 2026-09-01 — tap for who they are
At the centre
A team that slows down and reads every pull request and every line of code should expect only a 30 to 50 percent productivity lift from AI.
Holds Read this korrent →
The absence of a visible productivity jump from AI proves nothing, because a real ten percent uplift across the board would be impressive and almost invisible from outside.
Holds
Having the very best AI model and harness does not result in better or faster execution and can slow teams down
Holds
The very large productivity gains from agents require working with them directly; putting another human in between is too slow to preserve the gain.
Holds
Delivery will keep being slow until companies apply AI to the human, business-process half of it, not just to coding.
Holds
An AI coding factory combined with an old-style roadmap probably leads teams into the backlog, parity and churn traps at machine speed.
Holds
The AI research cycle from idea to experiment will likely soon be 10x faster, but that may not make researchers 10x more productive in the field's net understanding.
Holds
AI has already made sweeping mechanical changes cheap; the unsolved problem is getting the same productivity when adding features to an old, entangled codebase.
Holds
The massive AI build-out is the right thing to be doing, and the only thing that will slow it is supply.
Holds
95 percent of the software made in an age of abundance will be shitty, and shitty software is easy to deal with because it goes away.
Holds
A feature added to a codebase is extremely difficult to remove once other code is built on top of it.
Holds
A feature shipped in a product's official release is fair to judge, regardless of whether the company labels it a beta.
Holds
CMake tooling is missing a linter that could statically catch most CMakeLists.txt mistakes.
Holds
Comparing code coverage between passing and failing test runs is a cheap, effective way to localize a bug quickly.
Holds
Everyone is rethinking code reviews, deploys, and possibly observability
Holds
AI-assisted coding will generate a lot of low-quality output that developers will need to clean up, even as it also produces good results.
Holds
AI-generated code should be treated as untrusted until there is evidence it preserves the intended behavior.
Holds
As AI makes it easier to generate code, teams must delete code more aggressively or be overwhelmed by accumulated complexity.
Holds