REALITYWIPE

CROSS_SECTION_ANALYSIS

The Solo Compile

SURFACE BEHAVIOR

  • Three hours into the wrong rabbit hole, and the blocker's name still isn't in the team channel.
  • You draft the Slack question, add “sorry if this is dumb”, then delete the whole thing.
  • In design review you nod at the part you didn't follow and schedule the panic for later.

THE HIDDEN RULE

“A real engineer already knows, so every question is a confession and every 'I don't know' is a resignation letter.” This is the ask-vs-should-know bind, and it's why 52.7% of surveyed software engineers report frequent-to-intense impostor feelings while sitting on teams full of people quietly Googling the same things. The script converts the cheapest operation in engineering — asking — into the most expensive one.

INSTALL MECHANISM

Engineering Imposter Review Dread

Engineering imposter review dread is the anticipatory fear that a code review will expose one's perceived lack of competence to colleagues — not just that the code might have bugs, but that the review will confirm the reviewer's secret fear of being a fraud. Lee et al. (2024) found this is a measurable, distinct experience that leads to avoidance behaviors including delaying PRs, under-commenting code, and selectively avoiding certain reviewers.

REPLACEMENT PROTOCOL

  • “I don't know, let's find out” is a senior engineer's sentence. I just said it.
  • Blocked for three hours alone isn't rigor — it's a denial-of-service attack on my own sprint.
  • Asking is O(1). Pretending is O(n) and n grows every day I keep quiet.

STATUS: READY_TO_INSTALL

A senior engineer wouldn't have to ask this

Start this exact wipe in the app →