> SCANNING INSTALLED PROGRAMS...
> FOUND: THE INDISPENSABILITY PROOF
> STATUS: RUNNING — LOAD: HIGH
> RULE DECODED:
“If the system doesn't need me, the company doesn't either.” So designs get clever instead of simple, and critical work never gets handed off — you build job security the way you'd build a single point of failure, because that's what it is.
> ACTIVE THREADS: 2
> RESEARCH REFS FOUND:
> EXPLOIT VECTORS IDENTIFIED:
The velocity comparison trap is the cognitive pattern of using a peer's visible output speed — tickets closed, PRs merged, commits pushed — as a proxy for their overall productivit…
The 10x myth mechanism describes how a finding from a 1968 study of 12 programmers completing a single debugging task became a widely-repeated folk belief about a stable, identifia…
The overwork-burnout spiral describes the pattern in which the belief that longer hours signal dedication and capability drives engineers to push past sustainable limits, which inc…
> WIPE PROTOCOL AVAILABLE
STATUS: READY_TO_INSTALL
“The design has to be impressive, not simple”
Start this exact wipe in the app →RELATED CONTENT
SCRIPTS
- When handing off work feels like proof you weren't necessary
- The design has to be impressive, not simple | When simple feels too small
- "Every security issue makes me look like I'm not thorough"
- When You Won't Post Anything Less Than Flawless
- If It's Not Perfect, It's Worthless — Perfectionism Thought
- Every System I Built Could Have Been a Prompt: The Retroactive Erasure
- I'm not actually creative: The identity audit behind unfinished work
- I'm the Weakest Engineer in Every Meeting: Why That Thought Sticks
SCIENCE
- The Science of Engineering Incidents and Identity: Why It's Rarely the Villain's Fault
- The Science of Imposter Phenomenon in Software Engineering: Why It's Not Just Self-Doubt
- The Science of Creative Block: Why Waiting for the Muse Is the Block
- The Science Behind Designer Frustration: Client Override, Spec Work, and Portfolio Comparison
QUIZZES