The Patch Is a Cover StoryYou're three patches deep into the same billing module, another try/catch wrapped around a function nobody trusts, and the thought that stops you isn't 'this needs a rewrite.' It's that saying that sentence out loud would mean confessing the patches were never going to hold. So you keep believing the myth: proposing a rewrite equals admitting you personally couldn't just fix what's there, so the safer move is one more patch.
OLD SCRIPT DETECTED
“Rewriting it properly would mean admitting I can't just fix what's there”
Try this response:
“A rewrite isn't a confession. It's one option among several for code I didn't design.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“Rewriting it properly would mean admitting I can't just fix what's there”
YOUR RECORDED RESPONSE
“A rewrite isn't a confession. It's one option among several for code I didn't design.”
ONE PRIVATE MOVE
Write the private two-column list, repairable now versus needs rewriting, and save it somewhere only you can see it.
The Patch Is a Cover Story
Why the Rewrite Feels Like a ConfessionThe mechanism is anchoring: the moment you inherited this module, 'fix it in place' became your default frame, and every patch since has reinforced that frame as the only acceptable one. Naming a rewrite now would mean stepping outside the frame you anchored to on day one, not because the code disagrees, but because switching frames feels like reversing a decision you never consciously made.
The Private Ledger TestBefore your next patch, spend five minutes on a private two-column list: one column for parts you could genuinely repair in place, one for parts you'd only ever describe as 'needs rewriting.' Nobody sees it. If the second column stays short, the myth holds for now. If it keeps growing every time you look, that's information the next patch alone won't give you.
TRACE · 01/04
How this script runs you
- You draft rewrite proposals in your head but delete them before finishing the first paragraph.
- Every new patch to the module feels like proof you're still capable of 'just fixing' it, so you keep adding them.
- You avoid saying the word 'rewrite' in standup, even when a patch takes longer than a rewrite would.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Legacy Inheritance Script
If I ever say this needs a rewrite instead of a fix, I'm confessing I couldn't handle what I inherited, so I owe it one more patch before I'm allowed to say that out loud.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- A rewrite isn't a confession. It's one option among several for code I didn't design.
- Patching and rewriting are both maintenance. Neither one is a verdict on me.
- I can name what needs rewriting without promising I'll be the one who never patches again.
Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.
INSTALL · 04/04
The protocol, on one card
When I think
“Rewriting it properly would mean admitting I can't just fix what's there”
I say
“A rewrite isn't a confession. It's one option among several for code I didn't design.”
Then I do one thing
Write the private two-column list, repairable now versus needs rewriting, and save it somewhere only you can see it.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "Rewriting it properly would mean admitting I can't just fix what's there". Word for word — the wipe targets the sentence, not the vibe.
- Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
- Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
- Run the loop: play it every morning and night, log one proof action a day for 7 days.
Straight answers
What if writing down 'needs a rewrite' makes it feel official, like I've committed to something?
The list stays private and nothing changes because you wrote it. It's not a proposal, a ticket, or a promise, just information you can revise or delete whenever you want.
Doesn't avoiding the word 'rewrite' just mean I'm being careful with the team's time?
Being careful with time and avoiding a specific word are different things. You can decide patching is the right call for now without needing to never say 'rewrite' out loud.
What if the two-column list shows most of the module needs rewriting, not patching?
That's still just a list, not a decision. It tells you where your attention keeps landing, and what you do with that information is a separate choice you can make later, on your own time.
Related old scripts
I'm not maintaining it, I'm just enabling it by not rewritingWhy You Rewrite Their Work Instead of Naming the FixForce-pushing a fix feels like hiding the evidence: what the urge to rewrite really meansWhen Every Legacy Bug Feels Like Proof You're Not Good EnoughThe Hidden Standard: Why You Rewrote It Again
Related self-checks
Related science
The Science of Stay-at-Home Parent Identity: Why Leaving a Career for Caregiving Feels Like Losing YourselfThe Science of Founder Control Burden: Why Letting Go Isn't Weakness — It's What the Data Calls RationalThe Science of Returning From Parental Leave: Why 'Everyone Moved On' Isn't the Real Problem
Researchers to explore
Related mechanisms
The research behind this script
- Postmortem Culture: Learning from Failure — Google SRE, Google SRE Book, 2016
- Invisible Labor in Open Source Software Ecosystems — Champion et al., arXiv, 2024
- Stack Overflow 2025 Developer Survey: Trust in AI at an All-Time Low — Stack Overflow, 2025
- A Mosaic of Perspectives: Understanding Ownership in Software Engineering — arXiv, 2025