DEV Community

Discussion on: Politeness or Bluntness in Code Review? Settling the Matter Once and for All

Collapse
 
daedtech profile image
Erik Dietrich

I'm trying to resist the urge to write a novel on the subject of office politics, since it's both something I've talked a lot about on my blog for years, and, in its current corporate incarnation, the thing that eventually drove me out of employment and into working for myself. At any rate, I'd say the fatal flaw experienced by most groups aiming for "correctness as currency" would arise from issues where correctness is either unknowable or else non-existent due to subjectivity.

So, at any rate, I don't take what you're saying as naive at all, but rather the seed of a good mode for interaction. Because if correct is (currently) unknowable, that should result in extremely productive discussions of "this call seems subjective, so how could we run an experiment and measure it?"

For me, that approach tends to eliminate a lot of discord, in the polite vs. blunt arena, but in terms of human interaction in general. "Is this a good blog post" is a question that can quickly become a terminally stupid shouting match between respondents. But, what if you say, "good as measured by what -- time on the page, reader engagement, etc" you can then start to establish outcome-oriented metrics and have more productive conversations.