Tap a claim on the ring to put it at the centre.
← Deploying straight to production with no staging server is the right…
17 connected korrents · 16 moments from 14 Jul 2018 to 6 Oct 2026.
Everything filed under team size
team size
Everything filed under coding agents
coding agents
Everything filed under developer tools
developer tools
Everything filed under vibe coding
vibe coding 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: Deploying straight to production with no staging server is the right trade for a solo developer, because the speed is worth the risk. Deploying straight to production with no staging server is the right trade for a solo developer, because the speed is worth the risk. Last stated 2 years ago
20 Aug 2024
PL
Pieter Levels — holds since 2024-08-20 — tap for who they are
Same subject: He runs tests locally and pushes straight to main, DHH-style; there is no develop branch and main should always be shippable. — tap to centre the map on it He runs tests locally and pushes straight to main, DHH-style; there is no develop branch and main should always be shippable. Last stated 8 months ago
12 Feb 2026
PS
Peter Steinberger — holds since 2026-02-12 — tap for who they are
Same subject: You cannot mandate a tool developers dislike — they will quietly spin up the one they wanted. — tap to centre the map on it You cannot mandate a tool developers dislike — they will quietly spin up the one they wanted. Last stated 7 months ago
22 Mar 2026
NF
Nicole Forsgren — holds since 2026-03-22 — tap for who they are
Same subject: Letting a coding agent live-edit the production server works fine in practice. — tap to centre the map on it Letting a coding agent live-edit the production server works fine in practice. Last stated 4 months ago
28 Jun 2026
PL
Pieter Levels — holds since 2026-06-28 — tap for who they are
Same subject: Software engineers behave as though the world exists in the repository, and it does not: the world is production. — tap to centre the map on it Software engineers behave as though the world exists in the repository, and it does not: the world is production. Last stated 2 months ago
12 Aug 2026
CM
Charity Majors — holds since 2026-08-12 — tap for who they are
Same subject: Developers should strive to make their setups as vanilla as possible. — tap to centre the map on it Developers should strive to make their setups as vanilla as possible. Last stated 2 weeks ago
6 Oct 2026
KD
Kent C. Dodds — holds since 2026-10-06 — tap for who they are
Same subject: Trying to build everything at once with any platform is generally kind of a disaster. — tap to centre the map on it Trying to build everything at once with any platform is generally kind of a disaster. Last stated 4 months ago
9 Jun 2026
RG
Ron Goldin — holds since 2026-06-09 — tap for who they are
Same subject: Leaving a known production bug unfixed is the right call when the business impact is zero — my vibe-coded service crashes and still has fewer outages than LeetCode. — tap to centre the map on it Leaving a known production bug unfixed is the right call when the business impact is zero — my vibe-coded service crashes and still has fewer outages than LeetCode. Last stated 4 months ago
24 Jun 2026
NE
NeetCode — holds since 2026-06-24 — tap for who they are
Same subject: The way software gets built flipped in December: writing code yourself is now the exception, not the default. — tap to centre the map on it The way software gets built flipped in December: writing code yourself is now the exception, not the default. Last stated 7 months ago
20 Mar 2026
AK
Andrej Karpathy — holds since 2026-03-20 — 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 favours tiny teams of high-agency individual contributors with blurred roles, and the coordinating manager is not needed until it is time to polish. — tap to centre the map on it AI favours tiny teams of high-agency individual contributors with blurred roles, and the coordinating manager is not needed until it is time to polish. Last stated 2 years ago
25 Mar 2025
JZ
Julie Zhuo — holds since 2025-03-25 — tap for who they are
Same subject: AI-branded layoffs are not about AI; they are about badly run companies putting an AI label on having hired too many people. — tap to centre the map on it AI-branded layoffs are not about AI; they are about badly run companies putting an AI label on having hired too many people. Last stated 4 weeks ago
27 Sept 2026
MG
Molly Graham — holds since 2026-09-27 — tap for who they are
Same subject: An engineering manager should support six to eight engineers: fewer and they drift into being a tech lead, more and they can only be a coach. — tap to centre the map on it An engineering manager should support six to eight engineers: fewer and they drift into being a tech lead, more and they can only be a coach. 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
At the centre
Deploying straight to production with no staging server is the right trade for a solo developer, because the speed is worth the risk.
Holds Read this korrent →
He runs tests locally and pushes straight to main, DHH-style; there is no develop branch and main should always be shippable.
Holds
You cannot mandate a tool developers dislike — they will quietly spin up the one they wanted.
Holds
Letting a coding agent live-edit the production server works fine in practice.
Holds
Software engineers behave as though the world exists in the repository, and it does not: the world is production.
Holds
Developers should strive to make their setups as vanilla as possible.
Holds
Trying to build everything at once with any platform is generally kind of a disaster.
Holds
Leaving a known production bug unfixed is the right call when the business impact is zero — my vibe-coded service crashes and still has fewer outages than LeetCode.
Holds
The way software gets built flipped in December: writing code yourself is now the exception, not the default.
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 favours tiny teams of high-agency individual contributors with blurred roles, and the coordinating manager is not needed until it is time to polish.
Holds
AI-branded layoffs are not about AI; they are about badly run companies putting an AI label on having hired too many people.
Holds
An engineering manager should support six to eight engineers: fewer and they drift into being a tech lead, more and they can only be a coach.
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