4 ms·
> One is a constructive criticism, one is not. The other one is accusatory in tone and puts the user in a defensive position. Even a simple tweak to say "did y
by johnnyanmac 3y ago
> One is a constructive criticism, one is not.
The other one is accusatory in tone and puts the user in a defensive position. Even a simple tweak to say "did you consider this approach" is better than a direct "why did you do it this way/not that way"? So I argue the original form leans a bit away from constructive.
> I'm defending a more direct style that communicates the same message, not a difference message all together.
and unfortunately, that direct style has histories of being used to put down. Hence my allegory. Good intentions, but if you can't consider how that language was used by others in less savory ways, you will simply end up the same when you dismiss someone's personal concerns: Tonedeaf.
>If you're consistently authoring inadequate contributions
And here's the assumption that once again comes out of nowhere. Why are we assuming that the hostile employee is right and everyone else is dumb? There are very few cases where these kinds of workers are truly in the right, and those that do tend to have enough emotional intelligence to go on a tirade against every co-worker, as opposed to talking to a manager or director.
Complain up the ladder, not in your immediate radius. I'm assuming we're all competent professionals, so there's almost no reason to ever lash out at a co-worker over their code quality.
>some people understand that they're fulfilling a professional function in exchange for compensation and don't see that their feelings have anything to do with it.
Then they shouldn't care about their co-worker's code quality unless they are constantly asked to fix it. Which is a managerial problem, not a co-worker problem. Same matter applies.
- thegrimmest 3y ago> The other one is accusatory in tone I think you need to revisit the definition. There is nothing accusatory about "Why didn't you do it this way?". It's simple question with a simple answer in the format: "Because <reason>". Reading an accusatory tone from a perfectly neutral question, and then getting defensive about it, is exactly the sort of corporate culture that has no place in a productive environment. ChatGPT gave the following answer: > If I encountered the phrase "Why didn't you do it this way?" during a code review, I would likely assume a curious or neutral tone. To avoid miscommunications, we should all be at least as sane as ChatGPT. > has histories of being used to put down The whole point is to interpret the words as they are written, and with common definitions from the dictionary. Not to read tones into them that may not exist in the culture of the speaker. > assumption that once again comes out of nowhere I was responding to your quote: > You can't be negative 100% of the time If you're receiving 100% negative feedback, the first place I'd look is internally. A review process is a solicitation for criticism. It's you who is saying that a who clearly, directly, professionally, and constructively criticizes work is "hostile". > Then they shouldn't care about their co-worker's code quality unless they are constantly asked to fix it They should care when they are asked to review it, since that's the point of a review process.
- johnnyanmac 3y ago>I think you need to revisit the definition. There is nothing accusatory about "Why didn't you do it this way?" okay: >indicating or suggesting that one believes a person has done something wrong. I believe the definition is apt here. You believe something is done wrong so you open it up with an accusation of not doing it "this way". It's almost textbook definition. There could be room for context, but in a vacuum it's not best to open up your review with "why didn't you X?". You should have established X while triaging the task. >ChatGPT gave the following answer: If there's one thing I'm not going to rely on an AI for, it's for human tone. Even advanced sci-fi sentient android have the stereotype of not capturing tone properly. So there's little point in trusting 2023 web scraping. It says it's a neutral tone because somewhere in its training data there is a person who assumed a neutral tone. Which in and of itself is subjective. It's based on the AI's limited experience on the internet, and the Internet is also infamously horrible at conveying tone. back in reality, I've been asked "why" so many times in an accusatory tone IRL that it's always going to put me on the defensive. "Why are you here?", "Why is this not done?", "Why are you late to this meeting?". It's not a good idea in general to do a cold open with that. >If you're receiving 100% negative feedback, the first place I'd look is internally. If you get negative feedback from everyone, sure If you get 100% negative feedback from a few specific persons, then it's probably personal. Especially if those few people are not your direct managers. Something we seem to both agree on is that we shouldn't take things personally in the workplace, but there often is a few people like that no matter where you go.
- thegrimmest 3y ago> You believe something is done wrong so you open it up with an accusation Nowhere is this belief stated in the text. It's simply not what the words mean. It is being fabricated entirely in your mind. The only appropriate thing to infer from a question is that the asker wants to know the answer. > I've been asked "why" so many times in an accusatory tone IRL that it's always going to put me on the defensive. The onus is on you to cope with that. Don't transfer this burden to everyone you communicate with. It's unprofessional. > If there's one thing I'm not going to rely on an AI for, it's for human tone. Sentiment analysis is actually something LLMs excel at.