The week-long ticket becomes your rankingYou open your own ticket and it already looks unfair: old code, weird edge cases, a pile of context you had to dig up. Then you notice someone else shipped in a day. The thought lands fast: he is simply better at this, and your slower week means you are lower on the board. The comparison feels tidy because it turns two different jobs into one verdict.
OLD SCRIPT DETECTED
“He ships in a day what takes me a week”
Try this response:
“Different tickets, different codebases, different luck. The benchmark is invalid.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“He ships in a day what takes me a week”
YOUR RECORDED RESPONSE
“Different tickets, different codebases, different luck. The benchmark is invalid.”
ONE PRIVATE MOVE
Open a note and list three concrete differences between your last hard ticket and one fast-shipped task you noticed today: codebase age, unknowns, and dependencies. Keep it private and stop at three.
When their merge looks like your verdict
The board is measuring the wrong thingThe speed scoreboard is seductive because it ignores what made each task hard. One person gets a greenfield fix; another gets the legacy tangle. The old idea that speed cleanly ranks people came from toy-task variance, where much of the difference belonged to the task itself, not the person doing it. That is why the fast merge can feel like evidence, even when it only reflects different codebases, different luck, and different starting points.
Try a private comparison that uses the same yardstickPick one thing you handled last quarter that used to take longer, and write it beside the same kind of task now: same type of work, same tools, less friction, or fewer unknowns. Do not compare your week to their day. Compare you to you, on a similar ticket. If the notes show progress, the thought was too blunt to be trusted as a full ranking.
TRACE · 01/04
How this script runs you
- You look at a teammate’s quick merge and feel your own week collapse into a single bad number.
- A messy legacy ticket feels like a character test, while their cleaner work feels like a personal advantage.
- After a fast ship, you start scanning new hires for whether they might make you look slow or replaceable.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Velocity Scoreboard
If someone else ships faster, the difference is probably talent, and my slower ticket means I rank below them. The work itself is treated as neutral, so I blame myself for the gap instead of the setup.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- Different tickets, different codebases, different luck. The benchmark is invalid.
- His week and my week ran on different hardware. I compare me to me, last quarter.
- A fast merge can be useful without being a verdict about me.
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
“He ships in a day what takes me a week”
I say
“Different tickets, different codebases, different luck. The benchmark is invalid.”
Then I do one thing
Open a note and list three concrete differences between your last hard ticket and one fast-shipped task you noticed today: codebase age, unknowns, and dependencies. Keep it private and stop at three.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "He ships in a day what takes me a week". 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 their quick ship feel like proof that I’m slower?
Because the mind turns visible speed into a clean ranking. A merge is easy to count; the hidden load of the task is not. That makes the comparison feel obvious even when it is mixing very different kinds of work.
What if the other person really is just more capable?
Sometimes people do work differently or have stronger pattern familiarity. This thought goes further than that: it treats one fast day as a full ranking of you. The better test is whether the same kind of work, under similar conditions, keeps taking the same amount of time.
Why not just ignore the comparison altogether?
Because the sting is real and the thought keeps showing up. Ignoring it usually leaves the private verdict in place. A small written comparison gives the feeling somewhere concrete to land, without pretending every speed gap means something about your worth.
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