OLD SCRIPT DETECTED
“The bootcamp grad fixed it before my coffee even cooled”
Try this response:
“She'd seen that exact auth bug in her last job; I hadn't. That's the whole gap.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“The bootcamp grad fixed it before my coffee even cooled”
YOUR RECORDED RESPONSE
“She'd seen that exact auth bug in her last job; I hadn't. That's the whole gap.”
ONE PRIVATE MOVE
Before your next ticket, pour a coffee and jot the sip-count it takes to resolve it in a private note — no comparison, no sharing, just your own range across a few tickets.
The Ticket That Died Before the Coffee Did
The Pour-Over Still Steaming
You hand the flaky auth ticket to the new hire mostly to be nice — she did six months of bootcamp, you did four years of a CS degree. You pour a coffee, settle in to half-watch her flounder. By the time you've blown across the cup twice, her PR is up. The bug's dead. The coffee's still too hot to drink.
Re-Reading Your Own Diff Twice
For the rest of the week you open your pull requests before submitting them and reread every line like a stranger's going to grade it. You stop asking her clarifying questions in case the wrong one confirms what her speed already implied. You start timing your own tickets against hers without telling anyone, and start avoiding the tickets she's likely to grab first.
The Coffee-Cup Log
Pour a coffee before you start your next ticket and don't look at the clock — just note, on a sticky note only you'll see, roughly how many sips it took to resolve it. Do it for three tickets this week, hers and yours both. A four-sip fix and a forty-sip fix sitting in the same log is the actual range, not a verdict on either of you.
TRACE · 01/04
How this script runs you
- You mentally file her diploma-less resume as the reason the fix doesn't count, even though the code shipped.
- You reread your own commits for typos before pushing, something you never did before she started.
- You quietly avoid claiming tickets in the queue she's already skimmed, so the comparison never gets made out loud.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Velocity Scoreboard
Formal credentials are supposed to guarantee the pace of your work, so when someone without them moves faster, the rule concludes your years of training bought you nothing — instead of questioning whether ticket speed ever measured training in the first place.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- She'd seen that exact auth bug in her last job; I hadn't. That's the whole gap.
- My degree taught me things this ticket never touched. Neither number tells the whole story.
- A four-sip fix and a forty-sip fix can both be correct work. Speed isn't the grade.
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 bootcamp grad fixed it before my coffee even cooled”
I say
“She'd seen that exact auth bug in her last job; I hadn't. That's the whole gap.”
Then I do one thing
Before your next ticket, pour a coffee and jot the sip-count it takes to resolve it in a private note — no comparison, no sharing, just your own range across a few tickets.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "The bootcamp grad fixed it before my coffee even cooled". 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 a coworker's bootcamp background make her speed feel like more of a threat than a senior engineer's would?
A senior's speed reads as expected experience; a recent bootcamp grad's speed reads as proof the years you spent on formal training weren't necessary, which is a harder thing to sit with even though neither actually settles what your training was for.
Is it a problem that I started rereading my own pull requests twice after watching her close that ticket so fast?
Double-checking work is fine on its own, but if it started specifically after her fix and it's driven by dread rather than care, it's worth noticing that the habit is answering her speed, not improving your code.
What does timing my own tickets against a coffee cup actually show me that a leaderboard doesn't?
A leaderboard ranks people against each other on one ticket; a private sip-count across several of your own tickets shows you your own range, which is the only number that was ever relevant to your work.
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