Tap a claim on the ring to put it at the centre.
← A healthy on-call schedule needs six or more engineers if every alert…
15 connected korrents · 12 moments from 14 Jul 2018 to 19 Sept 2026.
Everything filed under team size
team size
Everything filed under management
management
Everything filed under software quality
software quality
Everything filed under aviation
aviation
Everything filed under design
design 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 healthy on-call schedule needs six or more engineers if every alert is to be taken seriously by an engineer focused mainly on on-call and stability. A healthy on-call schedule needs six or more engineers if every alert is to be taken seriously by an engineer focused mainly on on-call and stability. Last stated 2 months ago
3 Sept 2026
GO
Gergely Orosz — holds since 2026-09-03 — tap for who they are
Same subject: A sustainable on-call rotation needs seven or eight engineers. — tap to centre the map on it A sustainable on-call rotation needs seven or eight engineers. Last stated 4 years ago
30 Jun 2022
CM
Charity Majors — holds since 2022-06-30 — tap for who they are
WL
Will Larson — holds since 2018-07-14 — tap for who they are
Same subject: On-call is part of an engineer’s job rather than something to be paid extra for, except where paying for it is the only way to make management fund the reliability work. — tap to centre the map on it On-call is part of an engineer’s job rather than something to be paid extra for, except where paying for it is the only way to make management fund the reliability work. Last stated 4 years ago
30 Jun 2022
CM
Charity Majors — holds since 2022-06-30 — tap for who they are
Same subject: Being woken up two or three times a year on call is reasonable, and more than that is a management failure rather than an engineering one. — tap to centre the map on it Being woken up two or three times a year on call is reasonable, and more than that is a management failure rather than an engineering one. Last stated 4 years ago
30 Jun 2022
CM
Charity Majors — holds since 2022-06-30 — tap for who they are
Same subject: A permanently painful on-call rotation is a five-alarm emergency, not a normal cost of owning code in production. — tap to centre the map on it A permanently painful on-call rotation is a five-alarm emergency, not a normal cost of owning code in production. Last stated 4 years ago
30 Jun 2022
CM
Charity Majors — holds since 2022-06-30 — tap for who they are
Same subject: In a safety-critical industry the regulator should be recruited onto the team early, so that it is you and the regulator against the problem. — tap to centre the map on it In a safety-critical industry the regulator should be recruited onto the team early, so that it is you and the regulator against the problem. Last stated 3 months ago
28 Jul 2026
BS
Blake Scholl — holds since 2026-07-28 — tap for who they are
Same subject: Work should be broken into manageable chunks, and a designer should not send an engineer a 500-line PR they did not even review themselves. — tap to centre the map on it Work should be broken into manageable chunks, and a designer should not send an engineer a 500-line PR they did not even review themselves. Last stated 5 months ago
26 May 2026
AM
Andy Madrick — holds since 2026-05-26 — tap for who they are
Same subject: A few senior individual contributors can be paid VP money and still cost less than the layered product org they replace. — tap to centre the map on it A few senior individual contributors can be paid VP money and still cost less than the layered product org they replace. Last stated 3 months ago
2 Aug 2026
TV
Tom Verrilli — holds since 2026-08-02 — tap for who they are
Same subject: A functionally organised engineering team seizes up at around a hundred people, because every feature then has to be negotiated against every other team's bandwidth. — tap to centre the map on it A functionally organised engineering team seizes up at around a hundred people, because every feature then has to be negotiated against every other team's bandwidth. Last stated 7 months ago
1 Apr 2026
TP
Thuan Pham — holds since 2026-04-01 — tap for who they are
Same subject: A group of fewer than four people is not a team: it behaves like a set of individuals, and a single departure knocks it back into maintenance. — tap to centre the map on it A group of fewer than four people is not a team: it behaves like a set of individuals, and a single departure knocks it back into maintenance. Last stated 8 years ago
14 Jul 2018
WL
Will Larson — holds since 2018-07-14 — tap for who they are
Same subject: AI gives an individual contributor so much leverage that one very senior product manager beats three entry-level ones. — tap to centre the map on it AI gives an individual contributor so much leverage that one very senior product manager beats three entry-level ones. Last stated 3 months ago
2 Aug 2026
TV
Tom Verrilli — holds since 2026-08-02 — tap for who they are
Same subject: With AI handling routine tasks, the high-value human work of understanding client needs and trade-offs can be done by a smaller, more proactive team. — tap to centre the map on it With AI handling routine tasks, the high-value human work of understanding client needs and trade-offs can be done by a smaller, more proactive team. Last stated a year ago
11 Jun 2025
JF
Jacob Falkovich — holds since 2025-06-11 — tap for who they are
Same subject: With AI tools, in-house development teams can do more and need less rented developer capacity. — tap to centre the map on it With AI tools, in-house development teams can do more and need less rented developer capacity. Last stated a month ago
19 Sept 2026
GO
Gergely Orosz — holds since 2026-09-19 — tap for who they are
Same subject: As a small design team, you should not stand in the way of engineers designing with coding agents but find ways to support them. — tap to centre the map on it As a small design team, you should not stand in the way of engineers designing with coding agents but find ways to support them. Last stated a month ago
15 Sept 2026
NF
Nev Flynn — holds since 2026-09-15 — tap for who they are
Same subject: One person with many agents is probably not the right answer; the better bet is two-pizza teams made more effective, with pairs of humans steering the agents together. — tap to centre the map on it One person with many agents is probably not the right answer; the better bet is two-pizza teams made more effective, with pairs of humans steering the agents together. Last stated 7 months ago
7 Apr 2026
MF
Martin Fowler — holds since 2026-04-07 — tap for who they are
Same subject: Two people with agents can reach enterprise-grade codebase complexity in weeks -- what took organisations years, and they at least adapted to it as it grew. — tap to centre the map on it Two people with agents can reach enterprise-grade codebase complexity in weeks -- what took organisations years, and they at least adapted to it as it grew. Last stated 7 months ago
25 Mar 2026
MZ
Mario Zechner — holds since 2026-03-25 — tap for who they are
At the centre
A healthy on-call schedule needs six or more engineers if every alert is to be taken seriously by an engineer focused mainly on on-call and stability.
Holds Read this korrent →
A sustainable on-call rotation needs seven or eight engineers.
Holds
On-call is part of an engineer’s job rather than something to be paid extra for, except where paying for it is the only way to make management fund the reliability work.
Holds
Being woken up two or three times a year on call is reasonable, and more than that is a management failure rather than an engineering one.
Holds
A permanently painful on-call rotation is a five-alarm emergency, not a normal cost of owning code in production.
Holds
In a safety-critical industry the regulator should be recruited onto the team early, so that it is you and the regulator against the problem.
Holds
Work should be broken into manageable chunks, and a designer should not send an engineer a 500-line PR they did not even review themselves.
Holds
A few senior individual contributors can be paid VP money and still cost less than the layered product org they replace.
Holds
A functionally organised engineering team seizes up at around a hundred people, because every feature then has to be negotiated against every other team's bandwidth.
Holds
A group of fewer than four people is not a team: it behaves like a set of individuals, and a single departure knocks it back into maintenance.
Holds
AI gives an individual contributor so much leverage that one very senior product manager beats three entry-level ones.
Holds
With AI handling routine tasks, the high-value human work of understanding client needs and trade-offs can be done by a smaller, more proactive team.
Holds
With AI tools, in-house development teams can do more and need less rented developer capacity.
Holds
As a small design team, you should not stand in the way of engineers designing with coding agents but find ways to support them.
Holds
One person with many agents is probably not the right answer; the better bet is two-pizza teams made more effective, with pairs of humans steering the agents together.
Holds
Two people with agents can reach enterprise-grade codebase complexity in weeks -- what took organisations years, and they at least adapted to it as it grew.
Holds