QUIET
Quiet signal
“If the code is bad, maybe I'm bad at evaluating code” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “The code can be weak without my read on it being weak.”
SCRIPT CHECK · 60 SECONDS
“If the code is bad, maybe I'm bad at evaluating code”
See what this thought is changing.
Five quick questions show how often it appears, how believable it feels, and what it makes you avoid. You’ll get one private next step.
What this self-check measures
This is not a diagnosis and there is no pass or fail. It measures the current frequency, credibility, and behavioral cost of “If the code is bad, maybe I'm bad at evaluating code”, including the private rule underneath it: Under this thought sits a private rule: if the code turns out to be bad, then my judgment must be on trial too. So you treat uncertainty about the code as uncertainty about your competence, and you keep searching for enough certainty to…
See all result bands
PRESENT
Present in the background
“If the code is bad, maybe I'm bad at evaluating code” wins some small decisions before you catch it. Your useful interruption is: “I can be unsure about this structure and still be a solid evaluator.”
ACTIVE
Active pattern
“If the code is bad, maybe I'm bad at evaluating code” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: Open one old file or review thread you already have access to and write two private columns in a note: 'code signals' and 'my signals.' Add three items to each without changing anything else.
DOMINANT
Getting the final word
Right now, “If the code is bad, maybe I'm bad at evaluating code” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: Open one old file or review thread you already have access to and write two private columns in a note: 'code signals' and 'my signals.' Add three items to each without changing anything else.