Conflict Resolution in Code Review and in Life

Code review is conflict management with a technical object in the middle — and the diff is the table, not the battlefield.

A mystic-bytes essay rewrite stalled last week when comments read as verdicts on my voice instead of questions about the mechanism paragraph. I had done the same thing from the other chair: defending lines as if the lines were me. Both modes burn hours and teach nothing. When we moved the thread back to the draft — “does this brief match the body?” instead of “is this how you write?” — the pass finished in one sitting.¹ The artifact is neutral. The conversation around it is not. Reviewers who anchor on the code ask testable questions; authors who respond with alternatives keep the conflict on the system.

Propose a different structure the way you would offer a colleague another route on a map.

The review ends when the system is better — not when someone wins.

— JV · Dark Heart Labs.

Karl E. Weick, Sensemaking in Organizations (SAGE, 1995) — on separating identity from the object under discussion when groups negotiate meaning. ↩