QUIET
Quiet signal
“He ships in a day what takes me a week” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “Different tickets, different codebases, different luck. The benchmark is invalid.”
SCRIPT CHECK · 60 SECONDS
Five quick questions show how often it appears, how believable it feels, and what it makes you avoid. You’ll get one private next step.
This is not a diagnosis and there is no pass or fail. It measures the current frequency, credibility, and behavioral cost of “He ships in a day what takes me a week”, including the private rule underneath it: 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.
QUIET
“He ships in a day what takes me a week” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “Different tickets, different codebases, different luck. The benchmark is invalid.”
PRESENT
“He ships in a day what takes me a week” wins some small decisions before you catch it. Your useful interruption is: “His week and my week ran on different hardware. I compare me to me, last quarter.”
ACTIVE
“He ships in a day what takes me a week” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: 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.
DOMINANT
Right now, “He ships in a day what takes me a week” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: 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.