You Ship Bad Software Because You're Nice

Being 'nice' in engineering teams — softening code reviews, staying silent in architecture meetings, avoiding hard truths — is a form of ruinous empathy that directly causes production failures and technical debt. Drawing on Kim Scott's Radical Candor framework, Google's Project Aristotle, and real-world cases like Knight Capital's $440M loss, the argument is that high-performing teams have more conflict, not less, but it's idea-focused rather than personal. Practical techniques include writing positions before discussions, running premortems, and using written review before verbal discussion. The career angle: candid technical communication is the primary skill separating senior engineers from staff-level roles, and developers who avoid it rarely advance beyond senior.