OLD SCRIPT DETECTED
“The PR comments will reveal I'm a fraud”
Try this response:
“The review is about this change, not my worth.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“The PR comments will reveal I'm a fraud”
YOUR RECORDED RESPONSE
“The review is about this change, not my worth.”
ONE PRIVATE MOVE
Open the PR privately, copy the first reviewer comment into a scratch note, and rewrite it in plain language as a task the code needs in under ten minutes.
When the comments land
- The red dots feel personalYou see the PR still sitting there and the comments badge looks less like feedback than a warning light. You start reading every line as if it will expose the thing you’ve been trying to keep hidden: that you don’t really belong in the role, and this review is where people finally notice. So you wait. You re-open the diff, close it, and let the draft linger because a visible PR feels safer than a reviewed one.
- This is a review of the work, not a trialThe comments may be sharp, brief, or annoyingly specific, but they are still about the code in front of you. They can mean confusion, style, missing context, or a better way to do it. They do not automatically add up to fraud. If the review is uncomfortable, that doesn’t make it a confession. It means another person is looking at the same change from the outside.
Read the first comment, not the whole verdict
You choose a small, private next step: open the PR, read only the first comment slowly, and write a one-line note under it about what it actually asks for. No arguing, no hiding, no deciding what it says about you. Just separate the fix from the fear. Then you can handle the next comment the same way, one line at a time.
TRACE · 01/04
How this script runs you
- The PR stays in draft for days, not because the code is unfinished, but because being seen feels riskier than being wrong.
- You reread reviewer comments for tone, looking for the moment the feedback turns into proof that you’ve been found out.
- A single “why did you do it this way?” keeps echoing long after the rest of the thread is quiet.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Review Trial
If the review is visible, you are visible. If someone questions the code, they are questioning your competence, your right to be there, and the whole story of how you got here. Better to stall, over-prepare, or disappear than let comments become evidence.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- The review is about this change, not my worth.
- A hard comment can still be a useful comment.
- I can fix the code without turning it into a verdict.
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 PR comments will reveal I'm a fraud”
I say
“The review is about this change, not my worth.”
Then I do one thing
Open the PR privately, copy the first reviewer comment into a scratch note, and rewrite it in plain language as a task the code needs in under ten minutes.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "The PR comments will reveal I'm a fraud". 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
What if the comments are blunt enough to feel humiliating?
Blunt feedback can sting without being a statement about who you are. The useful move is to translate the comment into the smallest concrete request it contains. You do not have to enjoy the tone to handle the task.
What if there are so many comments that it feels hopeless?
A long thread can feel like one huge accusation, but it is usually a stack of separate issues. Reading and naming only the first one keeps the whole review from collapsing into a single story about you.
What if I still feel like delaying the PR?
Then the goal is not confidence; it is contact with the work. A short private pass—opening the thread, naming one request, making one note—breaks the spell of “they see through me” without forcing a bigger move.
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