The clock you're actually readingYou paste your problem into the AI at 4:47pm. By 4:47:20 there's a full answer on screen, and the version you built over the last hour suddenly looks like it took too long. The myth is that the stopwatch is measuring the same thing twice — that twenty seconds of generation and sixty minutes of your work are two attempts at one task, and the faster one wins by default.
OLD SCRIPT DETECTED
“An hour of my work, generated in seconds”
Try this response:
“Twenty seconds and one hour aren't measuring the same task — one of them skipped the part where I decide if it's right.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“An hour of my work, generated in seconds”
YOUR RECORDED RESPONSE
“Twenty seconds and one hour aren't measuring the same task — one of them skipped the part where I decide if it's right.”
ONE PRIVATE MOVE
Time yourself reviewing your last AI-assisted output for errors, then compare that number honestly to the twenty seconds it took to generate.
The stopwatch you didn't mean to start
Why the timer feels like a verdictThe research behind this program describes a fast burn, not a slow one: watching generated work outpace built work again and again reframes your hour as waste before you've even judged the output. Nothing in that comparison accounts for the parts that don't show a timestamp — the seconds you spent last week rejecting a similar answer, or the context that told you which twenty-second draft to trust and which to bin.
Racing the clock against itselfPull up the last thing you built in under an hour and the last AI output you accepted without changes. Time how long you spent reviewing each one before you trusted it, not making it. If the review times land closer together than the build times did, the twenty-second number was never the honest measurement — your judgment time was.
TRACE · 01/04
How this script runs you
- You catch yourself mentally re-running the last hour's work as '20 seconds, if I'd just asked first.'
- You've started timing your own tasks against how fast you guess the AI would finish them, even when no one's watching.
- You describe a task as 'taking an hour' with an apologetic tone, as if the hour itself needs defending.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The AI Obsolescence Script
If a machine can produce the same output faster, the time I spent must have been wasted — as though speed alone decides whether work counted.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- Twenty seconds and one hour aren't measuring the same task — one of them skipped the part where I decide if it's right.
- The stopwatch only counts typing. It doesn't count the minutes I'd have spent finding out the fast answer was wrong.
- My hour bought judgment the twenty-second version doesn't have yet. That's not the same currency as speed.
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
“An hour of my work, generated in seconds”
I say
“Twenty seconds and one hour aren't measuring the same task — one of them skipped the part where I decide if it's right.”
Then I do one thing
Time yourself reviewing your last AI-assisted output for errors, then compare that number honestly to the twenty seconds it took to generate.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "An hour of my work, generated in seconds". 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
Isn't it still true that the AI produced a working answer faster than I did?
Often, yes — generation speed is real. But 'produced an answer' and 'produced a trustworthy answer' aren't the same event, and only the second one is comparable to your hour of work.
What if I compare my hour to the AI's output and mine is genuinely worse?
Then you've learned something narrow and useful about that one task, not a verdict on an hour of your work in general. A single comparison tests a myth; it doesn't retry your whole skill set.
Why does watching the twenty-second generation feel worse than just reading the output later would?
Watching it happen live turns a document into a race you didn't enter, with your hour as the visible competitor. Reading the same output later, without the countdown, tends to feel far less loaded.
Related old scripts
When Small Contradictions Trigger Full SuspicionHe ships in a day what takes me a week: why the comparison stings"I wasted years not learning this sooner": the AI-era regret spiral"Using the AI feels like cheating": what that thought is actually trackingWhen You Recalculate the Drive Time to Catch Them in a Lie
Related self-checks
Related science
Researchers to explore
Related mechanisms
The research behind this script
- Impostor Phenomenon in Software Engineers — Guenes et al., ICSE-SEIS 2024, 2024
- Understanding and effectively mitigating code review anxiety — Lee et al., Empirical Software Engineering, 2024
- Understand team effectiveness (Project Aristotle) — Google re:Work, 2016
- Psychological impacts of AI-induced job displacement among Indian IT professionals: a Delphi-validated thematic analysis — PMC, 2024