3 ms·
I think you're hitting a cultural barrier. In my country, if someone brought me something terrible, in a professional environment, I would tell them it's bulls
by shakna 9y ago
I think you're hitting a cultural barrier.
In my country, if someone brought me something terrible, in a professional environment, I would tell them it's bullshit, and go try again. And that would be fine and dandy, and expected. (I'd expect the same treatment of myself. And it has happened.)
I get the feeling, that in the US, you can't criticise. You have to use some political language to say you like it, whilst meaning you don't.
Linus is Finnish. He says what he means. And it's expected, and entirely acceptable.
There are a handful of nations around the world, where saying exactly what you mean is far more valued than trying to preserve whatever emotion someone has invested into their work.
- andreasley 9y agoQuestion is, is it constructive? Does ranting really yield better results than just stating the facts (both short term for fixing the problem and long term for working together)? It might work for Linus on the LKML, but it certainly doesn't for everyone and in all circumstances.
- shakna 9y ago> It might work for Linus on the LKML, but it certainly doesn't for everyone and in all circumstances. Exactly, it's cultural. And, I wouldn't call it ranting. If you look at Linus' famous examples of this, he may first call it bullshit (calling it as it is), and then he goes on to explain why it is, and usually also explains how to polish the turd into what it should have been. It certainly works in my experience, having been on both ends of this sort of communication. It tells you that your quality has fallen well and truly below the expected level of output. But it isn't something held against you either. Because in these same cultures, it is okay to make a mistake, even costly ones. Because they make you better. I've shown you that what you made is crap, and why it is crap. So now I know that you know that sort of thing is crap, and will strive to make something better. And you also know I won't turn around tomorrow and remind you of it, because you're passed it. Probably not even in jest.
- mrmondo 9y agoAs a Kiwi, living in Australia I totally agree and understand, during code review in ops if something crap - I’ll things like ‘hmm, this looks a bit crap, maybe refactor for improved readability?’ Or ‘this has code smell written all over it, we can’t accept this kind of quality into production’ - I could just as easily say ‘Ross, this is shit - just rewrite it’ and my not so hypothetical Ross in this situation would read that - probably laugh, agree and rewrite it the next day OR ask for clarification stating why he doesn’t think it’s shit. My point is, what matters is the product, the code, the result and the quality there of. The communication around it is entirely based on the relationship and expertise of those around you.