I'd love to say that I value directness, but I frankly just kinda don't, for the most part. I don't want people to overly obfuscate what they are saying or beat around the bush, but... I have feelings. Often my feelings aren't rational. Often I have feelings about things when I should be more detached. But that's just how I am.

I don't want someone to come up to me and say, "Your code is wrong; you should have done ABC". I want them to say "Hey, I ran into a problem with your code. I think here on line 123 you meant to do ABC but you did XYZ by accident. What do you think?"

I'm not a dispassionate, disinterested observer. I do have some attachment to the code I write. I know -- and admire -- people who don't, but I'm just not one of them. I like it when someone is polite when they point out my mistakes.

> I don't want someone to come up to me and say, "Your code is wrong; you should have done ABC". I want them to say "Hey, I ran into a problem with your code. I think here on line 123 you meant to do ABC but you did XYZ by accident. What do you think?"

It's also a sign of good faith and tentative analysis since while that example sounds cut and dry sometimes context/details can be overlooked even those familiar with something.

Even in the article while the headline and main text suggest they'd be happy with bluntness to the point of rudeness the actual full examples at the end show the language used is merely succinct while still being helpful, with the second example also substituting the more direct 'you' for the diffused 'we'.