Tap a claim on the ring to put it at the centre.
← A refactor often needs to be deployed anyway, to check that nothing has broken.
17 connected korrents · 17 moments from 10 Jul 2021 to 23 Sept 2026.
Everything filed under software quality
software quality
Everything filed under design
design
Everything filed under open source
open source
Everything filed under compilers
compilers
Everything filed under coding agents
coding agents 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 refactor often needs to be deployed anyway, to check that nothing has broken. A refactor often needs to be deployed anyway, to check that nothing has broken. Last stated 5 years ago
10 Jul 2021
ML
Marc Littlemore — holds since 2021-07-10 — tap for who they are
Same subject: A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting. — tap to centre the map on it A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting. Last stated 5 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: Refactors are cheap now, so he just does them, even when they break other people's open pull requests. — tap to centre the map on it Refactors are cheap now, so he just does them, even when they break other people's open pull requests. Last stated 8 months ago
12 Feb 2026
PS
Peter Steinberger — holds since 2026-02-12 — tap for who they are
Same subject: Needing to mock code in tests often signals an underlying design problem that refactoring would fix. — tap to centre the map on it Needing to mock code in tests often signals an underlying design problem that refactoring would fix. Last stated 5 months ago
15 May 2026
YX
Yihui Xie — holds since 2026-05-15 — tap for who they are
Same subject: Twitter needed refactors before features: a code base that bad has to be fixed before anything new is built on top of it. — tap to centre the map on it Twitter needed refactors before features: a code base that bad has to be fixed before anything new is built on top of it. Last stated 3 years ago
29 Jun 2023
GH
George Hotz — holds since 2023-06-29 — tap for who they are
Same subject: Veterans of the 1990s free software movement do not understand the world today’s maintainers work in, and should listen before proposing fixes for it. — tap to centre the map on it Veterans of the 1990s free software movement do not understand the world today’s maintainers work in, and should listen before proposing fixes for it. Last stated 3 years ago
1 Apr 2024
TD
Thomas Depierre — holds since 2024-04-01 — tap for who they are
Same subject: Well-functioning systems succeed through continuous debugging rather than perfect initial design. — tap to centre the map on it Well-functioning systems succeed through continuous debugging rather than perfect initial design. Last stated 2 months ago
20 Aug 2026
JP
Jennifer Pahlka — holds since 2026-08-20 — tap for who they are
Same subject: Needing forward deployed engineers because a product is too hard to use on its own is a bad sign. — tap to centre the map on it Needing forward deployed engineers because a product is too hard to use on its own is a bad sign. Last stated 2 months ago
23 Aug 2026
JA
Jen Abel — holds since 2026-08-23 — tap for who they are
Same subject: Release the first version of an open source project a little broken on purpose; nothing recruits collaborators like something they know how to fix. — tap to centre the map on it Release the first version of an open source project a little broken on purpose; nothing recruits collaborators like something they know how to fix. Last stated a year ago
12 Jul 2025
DH
David Heinemeier Hansson — holds since 2025-07-12 — 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 coding agent left to run over a weekend returns work that is half good, a quarter garbage and a quarter in need of repair. — tap to centre the map on it A coding agent left to run over a weekend returns work that is half good, a quarter garbage and a quarter in need of repair. Last stated a year ago
18 Aug 2025
CB
Clay Bavor — holds since 2025-08-18 — tap for who they are
Same subject: A developer using AI coding tools remains responsible for reviewing the code they ship. — tap to centre the map on it A developer using AI coding tools remains responsible for reviewing the code they ship. Last stated 7 months ago
10 Mar 2026
JS
Jon Seager — holds since 2026-03-10 — 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
Same subject: 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. — tap to centre the map on it 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: Agent-written code that runs and passes its tests is not enough: security, maintainability and being able to roll it back still need humans in the loop. — tap to centre the map on it Agent-written code that runs and passes its tests is not enough: security, maintainability and being able to roll it back still need humans in the loop. Last stated 4 months ago
7 Jun 2026
TF
Tony Fadell — holds since 2026-06-07 — tap for who they are
Same subject: Agentic code review raises the floor but cannot be trusted, because the model reading the code is the same model that wrote it, and it will tell you the code is great. — tap to centre the map on it Agentic code review raises the floor but cannot be trusted, because the model reading the code is the same model that wrote it, and it will tell you the code is great. Last stated 3 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — tap for who they are
At the centre
A refactor often needs to be deployed anyway, to check that nothing has broken.
Holds Read this korrent →
A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting.
Holds
Refactors are cheap now, so he just does them, even when they break other people's open pull requests.
Holds
Needing to mock code in tests often signals an underlying design problem that refactoring would fix.
Holds
Twitter needed refactors before features: a code base that bad has to be fixed before anything new is built on top of it.
Holds
Veterans of the 1990s free software movement do not understand the world today’s maintainers work in, and should listen before proposing fixes for it.
Holds
Well-functioning systems succeed through continuous debugging rather than perfect initial design.
Holds
Needing forward deployed engineers because a product is too hard to use on its own is a bad sign.
Holds
Release the first version of an open source project a little broken on purpose; nothing recruits collaborators like something they know how to fix.
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 coding agent left to run over a weekend returns work that is half good, a quarter garbage and a quarter in need of repair.
Holds
A developer using AI coding tools remains responsible for reviewing the code they ship.
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
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
Agent-written code that runs and passes its tests is not enough: security, maintainability and being able to roll it back still need humans in the loop.
Holds
Agentic code review raises the floor but cannot be trusted, because the model reading the code is the same model that wrote it, and it will tell you the code is great.
Holds