OLD SCRIPT DETECTED
“Nobody gets promoted for careful work”
Try this response:
“I’m paid for judgment, not for the fastest-looking version.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“Nobody gets promoted for careful work”
YOUR RECORDED RESPONSE
“I’m paid for judgment, not for the fastest-looking version.”
ONE PRIVATE MOVE
Open one unfinished work file you already have and add a private comment, note, or checklist item naming one specific risk, one cleanup you deferred, or one test you would add—without sending anything.
The version no one can see
The review queue
You’re staring at a pull request that’s basically ready, except for the part that still feels unfinished: one edge case, one naming cleanup, one test you could add if the day were wider. The little comment bubble keeps sitting there. Every minute it stays open makes the work feel less like judgment and more like delay, and the thought arrives fully formed: nobody gets promoted for careful work.
The shortcut that looks productive
So you trim the extra pass, ship the version that is easier to point at, and move on before the polish can slow you down. The cost is ordinary and annoying: you spend the next week circling back to the same awkward line, patching around something you already noticed, and feeling oddly exposed every time the rough spot comes up in a meeting or review.
The receipt on your desk
Take the file you keep meaning to “finish properly” and make one visible trace of care that nobody else has to approve: add the missing test, tighten one confusing name, or write a short note at the top of the draft listing the exact risk you already spotted. Keep it local. If you can point to the deliberate fix later, the thought has less room to claim that care never counts.
TRACE · 01/04
How this script runs you
- You start valuing the clean timestamp more than the cleaner decision, because the timestamp looks promotable.
- A lingering review feels like proof that careful work is costing you status, even when the work itself is solid.
- You reach for the version that can be shown quickly and leave the thoughtful part for “later,” where it often stays.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Presence Theater
If the work is slow to explain or hard to display immediately, it counts less than the version that looks done fast. Care is allowed, but only after the visible output is already safe enough to defend.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- I’m paid for judgment, not for the fastest-looking version.
- A careful fix can be the part that keeps this from getting redone later.
- If I can name the risk, I can still choose the stronger version.
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
“Nobody gets promoted for careful work”
I say
“I’m paid for judgment, not for the fastest-looking version.”
Then I do one thing
Open one unfinished work file you already have and add a private comment, note, or checklist item naming one specific risk, one cleanup you deferred, or one test you would add—without sending anything.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "Nobody gets promoted for careful work". 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 this thought show up most when the work is already close to done?
Because close-to-done work is where the contrast feels sharpest: the fast version is visible right away, while the careful version asks for one more pass that no one may notice. That makes the choice feel like speed versus safety, when it’s really a question of what kind of result you want to stand behind.
Does this mean I should ignore deadlines and polish everything?
No. The thought pushes you toward treating speed as the only thing that counts. The useful move is smaller: notice when you’re dropping care just to make the work look finished, and keep the one detail that prevents avoidable rework or confusion.
What makes a private action count as evidence against this thought?
Something observable that records care without needing anyone else’s response. A note about a risk, a missing test added, or one confusing label cleaned up all count because they show careful work has a real result, even when it doesn’t create a louder signal.
Related old scripts
Related self-checks
Related science
Researchers to explore
Related mechanisms
The research behind this script
- Productivity Variations Among Software Developers and Teams: The Origin of 10x — McConnell, Construx, 2020
- The SPACE of Developer Productivity — Forsgren, Storey, Maddila, Zimmermann, Houck & Butler, ACM Queue, 2021
- Burnout in software engineering: A systematic mapping study — Tulili, Capiluppi & Rastogi, Information and Software Technology, 2022
- Two Sides of the Same Coin: Software Developers' Perceptions of Task Switching and Task Interruption — arXiv, 2018