OLD SCRIPT DETECTED
“Every review comment is an IQ score”
Try this response:
“This comment is about the code, not my score.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“Every review comment is an IQ score”
YOUR RECORDED RESPONSE
“This comment is about the code, not my score.”
ONE PRIVATE MOVE
In under ten minutes, copy three review comments into a scratch note and rewrite each one as a neutral task label, such as “add test,” “clarify name,” or “check edge case.” Do not send anything; just cross off the rewritten items.
When the red badges start looking personal
The cursor freezes before the first comment
You open the review with a coffee gone lukewarm beside the keyboard and a row of comments already waiting. The words are ordinary enough — naming a variable, asking for a test, questioning a choice — but your stomach reads them like a score report. Every review comment is an IQ score, and now you are not looking at code so much as a silent ranking of how sharp you seem today.
The patch gets smaller, the draft gets older
After that, you start editing around the comments instead of through them. You rename one thing, then hover over the next note and close the tab. The PR stays in draft because it feels safer to keep it unfinished than to let the comments add up in public. By evening, you have spent more time rereading the thread than improving the code, and the simple work turns into a private audit of your intelligence.
A single line can tell a different story
Open the review and pick one comment that is purely about the code, not the person. Copy it into a note and rewrite it as a task in plain language: what changes, where, and nothing else. Then mark it done or cross it off. The point is not to feel confident; it is to create one visible fact that the comment was about a decision in the diff, not a verdict on you.
TRACE · 01/04
How this script runs you
- You read reviewer wording for hidden meaning, as if punctuation could reveal your rank.
- A few comments make you treat the whole PR like an intelligence test instead of a code check.
- You delay finishing because an unfinished draft feels less like being measured in public.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Review Trial
If the review sounds sharp, it means the reviewer has measured me and found me lacking. Each comment becomes evidence of where I stand, so I need to protect myself by reading less, delaying more, and treating silence as safety.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- This comment is about the code, not my score.
- I can answer the note without grading myself.
- A review can be noisy and still be useful.
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
“Every review comment is an IQ score”
I say
“This comment is about the code, not my score.”
Then I do one thing
In under ten minutes, copy three review comments into a scratch note and rewrite each one as a neutral task label, such as “add test,” “clarify name,” or “check edge case.” Do not send anything; just cross off the rewritten items.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "Every review comment is an IQ score". 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 comment really is blunt?
Blunt wording can still point to a code problem, a missing test, or a confusing choice. The tone may sting, but it does not automatically turn the note into a measure of your ability. Separating the task from the phrasing gives you something usable without adding a verdict.
Am I supposed to ignore how it feels?
No. The feeling is part of the scene. The pivot is not to pretend the comment feels neutral, but to stop letting the feeling decide what the comment means. You can notice the hit and still rewrite the note as work to do.
What if the comments keep piling up?
Then the review is probably asking for several changes, which is common work, not a secret ranking. A long list can mean the code needs more passes, more context, or a clearer shape. Count the tasks, not your worth, and deal with them one at a time.
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