5 ms·
You've obviously never worked in an office, or you have taken a big step away from reality. Perhaps you have never worked in a good office, on a good team wher
by nl 13y ago
You've obviously never worked in an office, or you have taken a big step away from reality.
Perhaps you have never worked in a good office, on a good team where people respect each other.
These people are kernel developers, not 4 year olds. If they commit code that is fucking stupid, they should be called fucking stupid for it.
Why? It's rude and additionally it doesn't seem to achieve anything positive that can't be achieved more politely.
- ricw 13y agoYes it can. Direct criticism leads to more honesty, leads to a more productive work environment. Just grow some balls and learn to deal with direct criticism..
- jonahx 13y agothis is a false dichotomy. the choice is not between "be polite and evasive" and "be honest and abusive". it's easy to be direct and honest without being abusive. see my example in another reply: https://news.ycombinator.com/item?id=6051057 https://news.ycombinator.com/item?id=6051057
- flumbaps 13y agoIt's not that hard to give honest direct criticism without being abusive. Not knowing the difference indicates that you're a terrible leader. Belittling anyone who refuses to tolerate abuse as needing to "grow some balls" is utterly ridiculous. I wouldn't work for anyone with your attitudes.
- nl 13y agoI appreciate direct criticism. Fortunately I also have enough balls to refuse to stand for people being rude to me. Politeness does not mean standing for incompetence.
- vacri 13y agoIt's rude and additionally it doesn't seem to achieve anything positive that can't be achieved more politely. It saves time when you don't have to carefully structure each criticism in a compliment sandwich and so forth. It's understood in this environment that that's how the story goes - the excerpts people see of 'linus being rude again' are tut-tutted by a bunch of people who've never read a single other message on the kernel mailing list.
- valleyer 13y agoIt’s not as black and white as you make it out to be. On one end of the spectrum, we have the inane “compliment sandwich”. On the other, we have Linus saying “your code is shit”. In the middle, we have professional yet effective criticism. Something like, “Sorry, we’re not going to take this code — it’s too half-baked and exposes some serious security vulnerabilities.”
- davidw 13y agoEven "your code is shit" is direct, but directed at the code, not the person. He seems to sometimes take it even farther and call people stupid, which just seems wrong to me. "This code is shit" seems like it'd be even better, as it takes even more of the 'you' out of it.
- scotty79 13y agoIt's technically different but in practice people react pretty much same way when you tell them they did something stupid and when you tell them they are stupid if it was propmpted by them doing someting stupid.
- rahoulb 13y agoI disagree - saying "that was a stupid thing to do" is very different to saying "you are stupid for doing that" and most people will notice that.
- ericd 13y agoInsulting the person probably serves as a filter - at that point that person either shapes up or stops committing, either of which is a better outcome for Linus than that person continuing to commit crap code for Linus to have to look at/approve. Your more reasonable comment doesn't have the same effect, so it's not the strictly better solution, depending on what Linus values.
- 13y ago