OLD SCRIPT DETECTED
“The model writes code faster than me — I'm obsolete”
Try this response:
“The model types faster. I decide what is true, safe, and ready to ship.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“The model writes code faster than me — I'm obsolete”
YOUR RECORDED RESPONSE
“The model types faster. I decide what is true, safe, and ready to ship.”
ONE PRIVATE MOVE
Pick one AI-assisted code block you’ve seen recently, copy it into a note, and label three separate lines: “keep,” “verify,” and “delete.” Do it privately and save the note without editing the original.
When the autocomplete feels like a verdict
The cursor keeps up, but you don't
You’re in a quiet room with one tab open and a code review draft beside it. The model finishes a function before you’ve settled on the edge case. The speed lands first, then the thought: The model writes code faster than me — I'm obsolete. The pace of the output gets treated like a measure of your future, not just the machine’s current turn of the crank.
You start protecting the old work
After that, you stop checking whether the new approach is cleaner and start defending the version you already had. A small spec change feels personal, so you keep polishing lines that may be thrown away. The day gets heavier, not because the code is hard, but because every replacement starts to feel like a replacement of you.
The receipt is what still belongs to you
Open a recent AI-generated snippet and add three private notes: what it gets right, what you would verify, and what you would not ship as-is. Save it as a plain text file or sticky note. If you can separate speed from judgment on paper, the thought loses its claim that pace alone decides your worth.
TRACE · 01/04
How this script runs you
- Every fast demo feels like a silent scoreboard, and you hear yourself losing before you’ve checked the result.
- A small requirements change can feel like proof that your earlier effort was foolish instead of simply outdated.
- You start tracking your value by lines produced, even though the machine will always beat that one measure.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Obsolescence Compiler
If a machine can produce the artifact faster, then the artifact — and the person who made it — are disposable. The private job becomes to outperform the model at speed, even though your real work is choosing what is correct, safe, and worth keeping.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- The model types faster. I decide what is true, safe, and ready to ship.
- Fast output is not final output. My judgment is part of the work.
- A changed draft does not erase me; it means the version improved.
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
“The model writes code faster than me — I'm obsolete”
I say
“The model types faster. I decide what is true, safe, and ready to ship.”
Then I do one thing
Pick one AI-assisted code block you’ve seen recently, copy it into a note, and label three separate lines: “keep,” “verify,” and “delete.” Do it privately and save the note without editing the original.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "The model writes code faster than me — I'm obsolete". 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
Why does speed feel like the whole story here?
Because the thought turns one visible trait — how fast code appears — into a verdict about your place in the work. That skips the parts humans are actually paid for: checking, choosing, and deciding what should survive.
What if the model really did write the first draft better?
Then the first draft did its job. A first draft is not the same as correct, maintainable, or safe. If the output needs review, your role has not disappeared just because the typing happened faster.
How is this different from thinking a spec change means I failed?
This thought goes further: it treats any replacement as evidence that you are replaceable too. The page names the narrower trap — speed becoming self-worth — rather than saying the changed spec made your work worthless.
Related old scripts
Related self-checks
Related science
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