En 30 secondes
Theo Browne describes “guilt-merging” a pull request because someone invested effort and the alternative is an uncomfortable conversation. He asks developers to question the things they have become accustomed to protecting.
- 1Guilt-mergingTheo asks whether developers have merged a pull request because its author worked hard on it.
- 2Avoided conversationThe change may not be quite right, but the alternative is a conversation the reviewer does not want to have.
- 3Reconsider prioritiesHe suggests questioning the things developers care about and whether they still matter.
À retenir
- A pull request can be merged out of discomfort rather than confidence in the change.
- The effort invested in a change can make a difficult conversation harder.
- Theo encourages developers to question whether their existing priorities still matter.
Lire le texte remanié, chapitre par chapitre
Why do we guilt-merge?
Theo describes merging an unsuitable change out of guilt. He calls for questioning the assumptions behind that behavior.
Who here has guilt-merged a pull request? Someone put a lot of work into it, and even though it was not quite right, you merged it anyway because the alternative was a conversation you did not want to have.
Why do we do this to ourselves? My point is that we care too much, and the things we care about are not necessarily the things that matter anymore. I hope we can start challenging some of those assumptions.
Sur la même chaîne
38:47EN
Theo - t3․gg· 28 oct. 2026Theo’s Long-Running Agent Experiments: Verification, Compute and CostTheo Browne · Ping LabsA skateboard game and two compiler projects show how repeated checks and flexible compute can sustain agent work—and how expensive those loops can become.
36:07ENTheo - t3․gg· 27 oct. 2026Theo on Token Costs, Coding Agents, and the Price of AI CapabilityTheo Browne · Ping LabsA viral estimate of Lauren's AI spending prompts a closer look at cache pricing, benchmarks, and the changing work of coding agents.
30:37ENTheo - t3․gg· 26 oct. 2026Theo’s Three Skills for Reviewing and Shipping with Coding AgentsTheo Browne · Ping LabsHow sol-loop, full-send and full-stop encode review, verification and different levels of merge authority.
0:43ENTheo - t3․gg· 23 oct. 2026Theo Distinguishes Security Vulnerabilities from Active AttacksTheo Browne · Ping LabsA short explanation of why disclosed software flaws and reported attacks are different kinds of security news.
29:22ENTheo - t3․gg· 22 oct. 2026Theo on Security Vulnerabilities, Stolen API Keys and AITheo Browne · Ping LabsA look at the gap between vulnerability disclosure and patching, and a speculative account of why stolen inference keys may be valuable.
31:13ENTheo - t3․gg· 20 oct. 2026Theo on Why Smarter Models Help More Than DevelopersTheo Browne · Ping LabsFrom game modifications to compiler experiments, Theo revisits his assumptions about who benefits from more capable AI.