OLD SCRIPT DETECTED
“The day feels wasted if I didn't get deep work in”
Try this response:
“A day measured only in solo focus time is using the wrong ruler for a collaborative job.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“The day feels wasted if I didn't get deep work in”
YOUR RECORDED RESPONSE
“A day measured only in solo focus time is using the wrong ruler for a collaborative job.”
ONE PRIVATE MOVE
Before you close the laptop tonight, write down two things that got decided, unblocked, or moved today because you were present — even without a focus block. Keep the note; don't send it anywhere.
Closing the laptop at 6pm with three meetings and no code merged
- 01 / The calendar you scroll at day's end
You close the laptop and scroll back through the day: standup, a design review that ran long, two Slack threads you had to untangle, a colleague's PR you talked through instead of writing your own. Nowhere in there is a stretch longer than forty minutes where you sat alone with the actual problem. The thought lands flat and certain: today didn't count. Not 'today was hard' — 'today was wasted,' as if the hours you spent unblocking someone else evaporate the moment you try to total them up.
- 02 / Why the tally keeps getting made
Counting the day this way gives you something to point at: a clean, private verdict instead of a fuzzy feeling. If deep work is the only entry that counts, you don't have to weigh how useful the review was or whether the thread you untangled saved someone else's afternoon — you just check the ledger and it says zero. The short-term payoff is that the guilt has a clear cause, which feels more manageable than the truth: a collaborative day resists being reduced to one column.
- 03 / Catching the tally before it closes
The moment to interrupt this is right when you start scrolling back through the day looking for the focus block. Instead of asking 'did I get deep work in,' ask what got unblocked, decided, or moved because you were in the room. Keep a running note of those moments as they happen, not just at 6pm. A day with three of those and no solo stretch is not the same as an empty one — it's just measured by a different instrument, and the ledger you've been using was never built to read it.
TRACE · 01/04
How this script runs you
- You scroll back through a day of reviews and threads looking for a focus block that never happened, and count the day a loss.
- You mentally discount time spent unblocking a teammate as if it doesn't belong on the same ledger as your own coding.
- You feel a specific dread at day's end that has nothing to do with what got shipped and everything to do with whether you sat alone with a problem.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Context-Switch Guilt
Only uninterrupted solo focus time counts as real work; everything else — reviews, help, decisions made in meetings — is invisible until I've logged at least one long stretch alone.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- A day measured only in solo focus time is using the wrong ruler for a collaborative job.
- What I unblocked today belongs on the same ledger as what I built.
- Zero long stretches doesn't mean zero — it means I need a different column to count it in.
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 day feels wasted if I didn't get deep work in”
I say
“A day measured only in solo focus time is using the wrong ruler for a collaborative job.”
Then I do one thing
Before you close the laptop tonight, write down two things that got decided, unblocked, or moved today because you were present — even without a focus block. Keep the note; don't send it anywhere.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "The day feels wasted if I didn't get deep work in". 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
If I keep letting reviews and threads eat the day, won't I eventually fall behind on the actual coding?
That's a real scheduling question, separate from whether today specifically counted. Falling behind is about the pattern across weeks, not whether one interrupted day gets zeroed out. You can protect more solo time going forward without needing to declare every fragmented day a failure first.
Doesn't unblocking someone else just mean I'm avoiding my own harder work?
Sometimes, but not by default. Avoidance has its own signature — you'd notice yourself seeking out the interruption before it arrived. A review that ran long or a thread that needed you isn't evidence of avoidance; it's evidence the day had more than one legitimate claim on your attention.
If I stop tallying by deep-work hours, how do I know a day actually went well?
Track what changed state — a decision made, a blocker cleared, a PR that can now merge — instead of hours spent alone. A day can produce real movement across three short interactions and no long stretch. The tally was never wrong to want evidence; it was just reading the wrong column.
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