The Cost of Looking Competent

A long-tenured engineer, Sophia, creates a widely adopted framework that becomes both a standard and a signal of her competence. When three engineers - one a recent hire - find bugs, anti-patterns, and over-engineered abstractions and propose substantial changes, leadership sides with Sophia and the framework remains largely unchanged. The piece uses this scenario to show how individual credit and ownership convert technical decisions into personal stakes: questioning a widely accepted design becomes a challenge to the person behind it, newcomers’ objections are dismissed more readily, and the organization risks mistaking defended authority for sound architecture. It also highlights how historical constraints that justified a pattern can become obsolete, leaving unnecessary friction or technical debt.

The argument calls for testing designs rather than targeting people. It recommends collecting objective data on where the framework creates friction, cataloging defects, explaining original constraints, and weighing repair versus replacement with a documented comparison of implementation effort, migration cost, regression risk, and maintenance implications. A neutral reviewer with authority should evaluate the evidence to avoid conflating deference with correctness. Finally, it warns that leadership incentives shape behavior: rewarding defense of past choices discourages learning, while rewarding evidence-based reversals preserves long-term engineering health.