3 ms·
I don't think it has to be that dramatic. The key is just avoiding the word "you" and not using laden words like "stupid" and "shitty." You're still free to sa
by asdfman123 7y ago
I don't think it has to be that dramatic. The key is just avoiding the word "you" and not using laden words like "stupid" and "shitty."
You're still free to say stuff like:
----------------
"I really fundamentally disagree with this approach and know it will lead to problems done the road. Let's talk through it in person."
Or "If we do this maintaining it in the future could be really hard. I veto it."
Or "This isn't going to work with our XYZ system. Please fix that and submit it again."
----------------
You can say a lot of things rather directly that way. You DON'T need to say things like:
----------------
"This is a f*ING awful idea!"
Or "What were you thinking?"
Or "This is horrible. Don't check in crap to our code base, think through things first."
----------------
Is it too great of an imposition to ask people to phrase things the first way? Honest question.
- stevens32 7y agoThis direct approach sounds really good, but seems dependent on having a certain personality to pull off without sounding aggressive. For those with low EQ, a shit sandwich is just easier to execute.
- zbentley 7y agoThen fix the low EQ, aka "not good at working with others". That's not the person beibg reviewed's fault.
- asdfman123 7y agoIt's not a personality. It's just posture. Just relax your body, and speak softly. It's actually quite simple. Relax, speak softly, literally just avoid the word "you" (it makes a difference), avoid loaded words. Be direct and be kind. That's it. I can't be convinced that software engineers, who can learn incredible amounts of technical details in a limited amount of time, can't learn that too. It's just a habit. Difficult to form, maybe, but good once you form it.