OLD SCRIPT DETECTED
“Junior devs with AI will leapfrog me”
Try this response:
“A junior with an AI tool can generate code fast. I can see which code is actually right. That's the difference.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“Junior devs with AI will leapfrog me”
YOUR RECORDED RESPONSE
“A junior with an AI tool can generate code fast. I can see which code is actually right. That's the difference.”
ONE PRIVATE MOVE
Take one piece of AI-generated code from today. Read it. Without running it, write a one-sentence reason to keep or reject it. If you can't name the reason in one sentence, read another piece until you can.
Watching the 20-second solution
- 01 / The output appears before your explanation
You're in a code review. A junior dev—three months into the job—pastes an AI-generated component. Twenty seconds total. You've already mentally outlined a two-hour build. You scan the output. It works. It's not how you'd structure it, but it works. You close the tab without commenting because you can feel the script starting: if the AI could do that in twenty seconds, what were those two hours ever for?
- 02 / Comparison feels like evidence of obsolescence
You start reaching for the AI first on small problems, telling yourself it's 'faster.' But you notice the pattern: when the output is good, you don't learn anything—you just copy it. When it's wrong, you fix it quickly and move on. The real cost is quieter: you stop explaining design tradeoffs to juniors because you realize you'd have to say 'I'd ask the AI first, then decide.' That sentence makes you sound replaceable. So you stop explaining, which means you stop thinking through it yourself, which confirms the fear: maybe a decade of learning is just expensive typing.
- 03 / Compare this code to your instinct, not to the AI's speed
Next time you see an AI output—yours or someone else's—do this: read the code for sixty seconds and make one decision: keep or reject. Write one sentence explaining why. You're not timing it against AI generation speed (that's rigged). You're measuring something real: can you see why that output is wrong, or right, in a way the AI can't explain itself? That judgment—knowing which code to throw away—is the skill that didn't change. The AI made the bad code faster, but your job of recognizing bad code is still there.
TRACE · 01/04
How this script runs you
- You watch an AI generate in seconds what took you planning, and you close your draft without comparing because 'it's already done.'
- A junior asks you how you'd solve a design problem, and you hesitate because admitting you'd use the AI first sounds like admitting you don't really know.
- You delete your own solution before running it, assuming the AI's output must be better just because it was faster.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The AI Obsolescence Script
If a junior can get to the same output with a tool, then my years of learning were just slow typing, and speed is the only skill that matters now.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- A junior with an AI tool can generate code fast. I can see which code is actually right. That's the difference.
- The AI didn't make the judgment part of my job easier—it made the bad code easier to spot.
- I spent years learning to debug code. Now I spend time understanding code I didn't write. Both are still the job.
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
“Junior devs with AI will leapfrog me”
I say
“A junior with an AI tool can generate code fast. I can see which code is actually right. That's the difference.”
Then I do one thing
Take one piece of AI-generated code from today. Read it. Without running it, write a one-sentence reason to keep or reject it. If you can't name the reason in one sentence, read another piece until you can.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "Junior devs with AI will leapfrog me". 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 they can prompt it, what's the difference between their speed and my experience?
Speed of generation versus accuracy of judgment. An AI can output ten solutions a minute. Knowing which one won't fail in production in six months is the skill. That only comes from having seen failures.
But a junior with AI might just get more done than me, faster.
Faster code that breaks doesn't count. Your actual job isn't 'generate code'—it's 'generate code that doesn't break.' Those are different jobs. The junior generates; you verify. That's not obsolete.
Doesn't the AI learning curve keep getting shorter, making my learning irrelevant?
The learning curve for *using* the AI is shorter. The learning curve for knowing which output to trust is still measured in years of seeing what breaks. You're conflating two different curves.
Related old scripts
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