OLD SCRIPT DETECTED
“A senior engineer wouldn't have to ask this”
Try this response:
“I don’t need to earn this question before I ask it.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“A senior engineer wouldn't have to ask this”
YOUR RECORDED RESPONSE
“I don’t need to earn this question before I ask it.”
ONE PRIVATE MOVE
Open a blank note and type one work question you have been avoiding, then add two bullet points: what you already checked and what is still unclear. Save it without sending or sharing it.
The Question You Delete Before It Exists
- 01 / The Slack draft with the apology already in it
It usually starts when you hit a small gap in the middle of work: a parameter name you don’t recognize, a design choice that doesn’t line up, a step in a review that everyone else seems to glide past. The question is ordinary. The thought is not: "A senior engineer wouldn't have to ask this." Suddenly the draft feels less like a request and more like evidence.
- 02 / Three tabs later, you still don’t have the blocker’s name
So you keep circling. You search docs, reread comments, re-open the same file, and tell yourself you just need one more pass before you ask. That delay buys a little relief: no one sees the question, and you get to keep the image of being the person who already knows. But the cost is hours spent alone with the wrong problem, while the blocker stays unnamed.
- 03 / The pause before you delete the whole thing
The interruption is not confidence. It is catching the private rule in real time: if a senior engineer asked, it would mean you failed. When that shows up, stop and write the question in plain language with no apology, just for yourself. Then add one line underneath: what you already checked. That split makes the ask concrete instead of moral.
TRACE · 01/04
How this script runs you
- You keep a question in draft form so long that the actual blocker becomes harder to name than the original confusion.
- A tiny gap in knowledge feels less like a normal handoff point and more like proof you should already be done.
- You would rather spend an afternoon cross-checking notes than let one plain question appear unfinished.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Solo Compile
The hidden rule is that competence should look effortless, so asking any question at the wrong moment will expose you as less senior than you seem. Under that rule, silence feels safer than clarity, even when silence is what keeps the work stuck.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- I don’t need to earn this question before I ask it.
- A senior engineer can still need a name for the blocker.
- I can write the question plainly and sort the rest after.
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
“A senior engineer wouldn't have to ask this”
I say
“I don’t need to earn this question before I ask it.”
Then I do one thing
Open a blank note and type one work question you have been avoiding, then add two bullet points: what you already checked and what is still unclear. Save it without sending or sharing it.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "A senior engineer wouldn't have to ask this". 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 this thought hit hardest in the middle of ordinary work?
Because the trigger is usually small: a comment, a field name, a review note, a line of code that doesn’t fit the pattern. The size of the issue stays small, but the meaning attached to asking gets huge, so the moment feels loaded before anything has actually gone wrong.
Why does keeping quiet feel better, even when it wastes time?
Because silence offers a short-term trade: you avoid the feeling of being seen asking for help, and you preserve the image that you should already know. The relief is immediate. The cost shows up later as more searching, more rereading, and more time spent protecting the question instead of solving it.
What is the point of writing the question down if I still might not ask it?
Writing it down separates the technical problem from the private verdict attached to it. Once the question exists on paper or in a note, it is easier to see what you need to know, what you already checked, and where the real blockage is. That often makes the next step feel less loaded, even if you keep it private.
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