A Software Engineer's Case Against Winning Arguments

A software engineer reflects on abandoning his long habit of arguing for technical correctness in code reviews, design meetings, and online threads. His core realization: most disagreements aren’t really about ideas but about ego. When you disprove someone’s position, they often experience it as a personal attack and dig in harder, so ‘winning’ produces a more entrenched opponent rather than a corrected mind. He argues people are fundamentally emotional rather than rational, reasoning backward to justify feelings they already hold, which makes airtight logic largely useless as a persuasion tool.

From this he draws practical rules for engineering and life: reserve genuine debate for smart people seeking the best answer, and walk away from ego-driven fights. Don’t volunteer corrections, because people learn from consequences, not advice—the only clean exception is when someone explicitly asks for help, which lowers their defenses and makes guidance land. Rather than persuading skeptics, he suggests treating disagreement as an asset: ship the thing others think is wrong and let reality settle it, a framing especially relevant to startups, whose entire value lives in the gap between what founders see and what the market hasn’t accepted.

The piece closes on a Stoic-flavored point that resonates in technical culture: you can only change yourself, so energy spent trying to convert others is stolen from self-improvement. The path to getting better isn’t winning debates but repeatedly asking for feedback and actually listening—turning the ‘only help when asked’ rule inward.