Re:Linus Torvalds: 'I'll never be cuddly but I can be more p...
by sonnyblarney on Thursday September 27, 2018 @04:59PM
(#18088615)
Totally disagree.
Saying something is 'problematic' is not remotely condescending. It's just a reasonably objective way of saying there are problems.
Saying something is 'crap' is neither more authentic nor more informative, it's absolutely not constructive and it certainly isn't polite.
I think you may have difficulty interpreting communication when you take things literally the opposite of what they are i.e. 'problematic' as some kind of 'crypto-speak' when it's not, and 'crap' - which is actually and objectively condescending and objectively not constructive.
If a piece of code needs work in a more general way, your manager's best option is to communicate that candidly in an impersonal and clear manner. Maybe with a tiny bit of sugar coating depending on the situation.
So 'the code needs a lot of work, specifically in these areas: a, b, c '. Or 'the code needs a lot of work and I see some ugly patters in there, maybe due to some habits you have developed elsewhere, let's work on these things specifically: a, b, c etc..' is appropriate.
The only time you can say code is 'crap' is when you have a very good relationship with someone, and a fair degree of mutual respect, and you also know that they'll never interpret it too negatively. As in 'heyzeus Joe that last checkin was abysmal, see: a, b and c ... and no more watching the pro-bowl while coding for you my man!' ... is what I could get away with someone I've known for quite a while.
You could use 'crap' in a public forum directed maybe at a group or company, but never publicly towards any individual.
If you're in charge of a major open source project, you can tell your staff that 'Joe from Montana's code is crap and we basically should ignore is pull requests' ... but you wouldn't say that to Joe himself.
Saying something is 'problematic' is not remotely condescending. It's just a reasonably objective way of saying there are problems.
Saying something is 'crap' is neither more authentic nor more informative, it's absolutely not constructive and it certainly isn't polite.
I think you may have difficulty interpreting communication when you take things literally the opposite of what they are i.e. 'problematic' as some kind of 'crypto-speak' when it's not, and 'crap' - which is actually and objectively condescending and objectively not constructive.
If a piece of code needs work in a more general way, your manager's best option is to communicate that candidly in an impersonal and clear manner. Maybe with a tiny bit of sugar coating depending on the situation.
So 'the code needs a lot of work, specifically in these areas: a, b, c '. Or 'the code needs a lot of work and I see some ugly patters in there, maybe due to some habits you have developed elsewhere, let's work on these things specifically: a, b, c etc..' is appropriate.
The only time you can say code is 'crap' is when you have a very good relationship with someone, and a fair degree of mutual respect, and you also know that they'll never interpret it too negatively. As in 'heyzeus Joe that last checkin was abysmal, see: a, b and c ... and no more watching the pro-bowl while coding for you my man!' ... is what I could get away with someone I've known for quite a while.
You could use 'crap' in a public forum directed maybe at a group or company, but never publicly towards any individual.
If you're in charge of a major open source project, you can tell your staff that 'Joe from Montana's code is crap and we basically should ignore is pull requests' ... but you wouldn't say that to Joe himself.