Hard Conversations — Disagreement, Pushback, Saying No, Escalation

Build the willingness, the preparation discipline, and the small toolkit of phrases for the conversations engineers most often avoid: disagreeing with peers, pushing back on managers and clients, saying no to scope, escalating when stuck, giving and receiving feedback with weight — and actually having the one you've been avoiding. Hard conversations are error escalation. In code you raise when the current scope can't responsibly handle the problem, with enough context that the rescuing scope can act; handle too low and you swallow the error silently, escalate too high and you lose context. Interpersonal escalation is the same judgment. The deprecation warning is the other lens: when a framework deprecates an API it doesn't silently break — it warns, gives a migration path, and lets you fix before the breaking version. Hard feedback works the same way: the first time a behavior is a problem, name it gently with a path; engineers who never give the deprecation warning deliver the breaking change at review time. And SBI is the linter cop: a rule that names a specific behavior and proposes a fix, mechanically, without the relationship having to bear the weight. The framework is the cop. Use it.