There is a particular kind of damage you can do when you are correct.

Not wrong. Correct. Factually, technically, demonstrably correct — and still leaving the room worse than you found it.

I’ve watched it happen in code reviews. Someone spots a genuine flaw. They’re right. The code has a problem. And instead of the fix being the point, the flaw becomes a verdict. The author feels exposed. The comment thread turns into a duel. The fix eventually lands, but something else broke in the process — something harder to debug than any null pointer.

Being right is the easy part. The question is what you do with it.

Stoicism has a concept worth sitting with: the discipline of desire. Epictetus is relentless on this. What we desire shapes our character, not just our outcomes. If you desire to be seen as correct more than you desire to solve the actual problem — you are already failing, even when you win the argument.

Fëanor was the greatest craftsman in Arda’s history. His Silmarils caught the light of the Two Trees in imperishable form, beauty the world had never held before. And on more than one occasion, he was right. Right that Melkor coveted the jewels. Right that the Valar’s counsel came with conditions. Right that the darkness spreading across Valinor was real and catastrophic. And yet his rightness lit a fire that consumed his house, his sons, and centuries of Elvish history. He swore his Oath under the stars — blazing with certainty — and became the instrument of his own ruin. Not because he was wrong. Because he was right in a way that left no room for anything else. Correctness without flexibility is just a different shape of blindness.

That’s the shape of the trap. Certainty that forecloses collaboration. Rightness that burns the trust needed to do the actual work.

In software teams, this plays out quietly. The senior who catches every mistake but whose reviews people dread. The architect whose designs are elegant but somehow never get built by a willing team. The person who is always the sharpest voice in the retro and somehow never makes things better.

There’s a version of competence that makes the room smaller. And a version that makes it larger. The difference isn’t accuracy. It’s whether you hold your correctness lightly enough that others can breathe around it.

Some fights need to happen. Some flaws need naming, loudly. But you should always know what you’re spending.

When was the last time you were technically correct — and it cost you more than being wrong would have?