it's possible to be succint, harsh, and directly to the point without swearing or being abusive. for example, off the top of my head:
"stephen, this code is riddled with basic errors and is completely unacceptable. please fix a, b, and c immediately and know that if you make mistakes like this again, your contributions will no longer be welcome."
versus:
"stephen, WHAT THE FUCK IS WRONG WITH YOU??!?! seriously, a FUCKING JUNIOR DEV would not make mistakes like this. why are you wasting my time with this FUCKING BULLSHIT? FIX IT NOW OR YOU'RE FIRED!"
imagine in both cases the person writing to you has only a professional relationship (ie, is not a friend who has the type of relationship with you where the 2nd paragraph would be an establish, half-joking form of communication)
honest open criticism != rude dick
It takes a little more work, because you have to think carefully about your words and calm down, but that action itself makes
a) the criticism more useful b) creates a frame where the criticism is more likely to be acted on and leave no resentment
Also, I believe that apologizing is something we should do more often. As in "I don't apologize for my behavior" is not as good a path as "I'm sorry I blew up, but I did have a point".
(Edit: My experience includes Fortune 100 in consumer tech and finance)
In this scenario Stephen has been hired to write code/produce something, I'll go all-Marxist on this and say he was hired to produce plus-value. He was not hired to be sworn at, no matter how good or bad his code/work might be, and this is why swearing directly at people is unprofessional.
As an aside, I'm surprised at the people who say that swearing to other people's face is "manly" (or something of the sorts). In the part of the world that I live if you swear someone directly in the face you'd better be prepared for a physical fight or worse.
the point is it's taken in a certain spirit, and you can't force people who don't know you well, or don't share that sensibility, to partake of that spirit.
even if you personally prefer that style, it's hard to argue that it's effective from a practical perspective. for the large majority of people, the first example is far more likely to actually get you your desired result than 2nd.
You are trying to create uniformity and conformance, which is not in our nature. Some people are polite, others are not (Linus for example). The working environment of the kernel mailing list is public and subject to harsh language because it's run (rather successfully it could easily be concluded) with the philosophy that people should be able to express themselves.
"you are trying to create uniformity and conformance, but people are different. some people are kind and patient with their children, others are explosive and sometimes beat them. some of those children grow up to be very successful and hit their children. who are you to tell people how to raise their children?"
to be clear, i am not saying linus's swearing in an email is even the same league as child abuse, but the logical argument above and the one you are making is the same.
honestly, it just seems like a clever piece of rhetoric to justify treating people any way you please. it reminds me of the evangelical christians here who are against gay marriage, and argue that they are the victims now because they can no longer preach against homosexuality in peace, and lobby for laws against it, what with all the liberal media painting them as monsters and not respecting their rights to express their own religious beliefs
When has Linus actually worked in an office? Would he really know what it's like?
AFAIK, he moved from Finland to USA in 1998 to work at Transmeta. He was already famous at that time, and presumably could dictate his working terms. I recall reading an interview that suggested he was mostly working from home on the Linux kernel already back then.
Maybe that's why his notion that "professionalism" equals neckties and backstabbing seems like a caricature out of a '90s TV show.
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.
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.
I can only imagine only the most socially incompetent people would actually find it a major time-sink to say things civilly. You don't have to make a compliment sandwich, saying "Your kernel patch throws a bunch of warnings, what the fuck is this?" is hell of a lot better than "which one of you retards can't read the guidelines?"
The basis of civility is to avoid personal attacks when it's not about the person. This isn't about the person. You can be civil and still be pissed off.
I was using the 'compliment sandwich' as a shorthand for reviewing all the commentary to make sure it's pleasant or polite. That stuff does take effort and time, particularly if you aren't intimately familiar with the other party and have to generalise it to the generic person. I've done a hell of a lot of support in my time and this is abundantly clear to me. There are even people who perform better when you swear around them, because they don't feel like they have to control their language.
Couched phrasing takes effort - and Torvalds is one of the few technocrats who still gets his hands dirty in the trenches.
The closest friend I'm with the more I swear. What I don't get is people awkwardly swearing in presence of people they just met. I see it as attempt to desperately get connection to other people.
Why are you apologizing?
The only reason being polite saves time is because someone is unpracticed at it.
This comment (and indeed your comment) are both polite and completely disagree. I spent a while thinking of how best to express my point, but none at all working out how to avoid being offensive.
But if it makes you feel better: fuck compliment sandwiches ;)
Politeness does not mean standing for incompetence.
In open source, the office is the mailing list. Life is tough. Say sorry and make sure it doesn't happen again. Move on - and outside the US, I think swearing is pretty common if you do something stupid - working environment or not. I don't think this means that we all have to adhere to US standards.
I'm guessing your co-workers knew you'd been chewed out but how much worse would you have felt (I guess plenty) and how much more would you have learned (I guess nothing) had your dressing down been in public?
Much of this isn't about some artificial standard for the sake of it, it's about getting the best out of people. Public beatings have been shown not to do that. If the OSS community wants to behave this way then it can but ultimately it's going to drive a bunch of people away, or cow them into not really speaking up for fear of retribution and as a result will likely miss out on valuable contributions.
There seems to be a thing here with a lot of people saying "I work like this and like it". That's fine but the worst mistake you can make with others is often assuming that everyone else is like you. a lot of management science is bullshit but alongside the nonsense there is actual quantitative research about how people behave and so on.
There is possibly a discussion to be had around whether programmers (or more strictly people with the potential to be good programmers as that's what you want to optimise for, rather than the people who are currently programmers) are typical but as a hypothesis I'd rather go with programmers behave broadly as other people do.
What is "it", exactly? Any public criticism? Public belittling (which is severely different from a proper dressing down)? Swearing? There's a lot mixed in here.
And does research conclusively establish a significantly different reaction to otherwise identical acts in public vs private?
> I'd rather go with programmers behave broadly as other people do.
Even if programmers behave broadly as other people do, that doesn't mean they'd have the same reaction to the same behavior in two very different scenarios.
Our dressing-downs[1] are as likely to come from our peers as our management. And even when they come from managers, we have a much different relationship with them. We are in positions of relative power and economic security, as well as positions of trust. A manager is more peer or patron than overlord, and we are more agent than minion. This is a very different dynamic than most jobs.
I question the relevance of any research on this that doesn't specifically target highly-skilled fields with economically-secure workers.
[1] Dressings down? Can you make bandages out of soft feathers?
Ultimately it depends on what you're trying to achieve when you're talking to someone. There might be occasions when being shamed in front of the team is the best thing for the person but I'd suggest that they're few and far between.
As a manager if I act angrily towards you then regardless of what you've done I'd suggest that I've both failed - yes you might have done something which has annoyed me but I've then responded by handling it badly. The best I can say at the end is that I didn't start it. The twice I've lost my temper publicly at a member of my team my overriding sense afterwards was that I should have handled the situation better. Certainly in neither case do I think what I did got the best from the person in question (one I think viewed the whole thing with complete indifference, the other was demotivated by it).
In terms of the specifics of the research, it's been a while since I looked at it (back in my days studying). I recall that public was generally a greater demotivator than private but I'm not aware of anything that's been done on different skill levels - would certainly be interested in that. My gut feel is that while there might be differences constructive engagement in private would still be the most productive way of handling it - I don't think programmers and other skilled workers are that different to the rest of the world. If anything I'd suggest they'd be more inclined to dislike anything involving anger directed at them - after all, they generally have the option to go elsewhere so why should they put up with it?
The comments you make about everything being out in the open are interesting. I can see if the manager or other berater is untrustworthy that this could be a thing, but if there are overall issues of trust of that type I think that how this sort of thing is handled is largely irrelevant in the face of that much larger problem.
You can't even trust yourself. You've "lost your temper" twice. Why won't you do it a third time? A fourth? A fifth?
Does it not occur to you that this is all just part of being human?
And yes, I've lost my temper twice and will probably do so again but as with those times when it has happened in the past I'll apologise, attempt to repair the damage and move on.
No-one needs to be perfect and unbiased, for the most part your flawed best with good intentions is plenty. If you find yourself working with people who don't have good intentions then maybe the level of suspicion is fair enough but personally I'd get the hell out of there rather than work in somewhere that poisonous - 20 years working has taught me that it's simply not necessary to put up with places like that and that there are plenty of alternatives.
I much prefer being publicly berated.
Okay, then add your real name to your Hacker News account so we can publicly berate you more effectively. :-)If someone commits code that is fucking stupid then by all means call the code fucking stupid. But then actually take the time to identify the cause for the mistake. Is that programmer following best practises? Are they being careless? Are they working on something they don't have the expertise for? Are they spread too thin? If you identify the problem you can try to fix it. Instead of abuse, you should be giving clear and direct instructions on how to not make mistakes like that ever again. If you call someone "fucking stupid" then you incorrectly identify the problem and, moreover, you're being abusive, which can be very harmful.
Calling someone stupid after he did something stupid is different than calling him that as a main point of his semiannual performance review.
Lying is dishonorable, counterproductive in context of multiple cooperating people, and a really bad idea overall, purely objectively. Swearing, linguistics-wise, is indeed a completely normal ("natural and ok") trait (present to some extent in individuals of all cultures, gender, professions etc., even in some higher animals) that is orthogonal to anyone's performance. How could you possibly equate these two is beyond me.
I'd say is a cultural thingie. Compared to other languages English has very few swear words/expressions, for example in my native language you could swear at someone by saying something like "fuck your mother's dead relatives" (it sounds way worse in original, trust me). If someone were to say that to my face my first instinct would be to see if I can beat him right there on the spot (and if yes, would I risk going to prison for hospitalizing him?) and if no then I'd think of swearing back with something even harsher (while looking for an escape route).
On the other hand everybody lies, that's why we have things like contracts etc, it's assumed that at some point or another we'll stop telling the truth.
I understand the whole "you've obviously never ..." thing that people do to state that their experiences are not representative, but it just sounds dickish in your post. I think it's pretty obvious that the person you are replying to has worked in an office, and has had a good dose of reality.
Why? Wouldn't you achieve the same thing by calling the commit fucking stupid? Why resort to personal attacks?
My Finnish colleague seems to like it. I'm told shouting "Perkele!" is a great stress-reliever.
Actually, he swore in Finnish in that post, and as a Swedish-speaking Finn, Swedish, and not Finnish, is his native language.
http://www.muktware.com/news/2857/which-linus-torvalds%E2%80...
This obviously doesn't hold true for all individuals, but Americans tend to prefer the "Let's all hold hands and sing kumbaya" type of social dynamic. "If you don't have something nice to say, don't say anything." Much emphasis is placed on not hurting anyone's feelings, and maintaining the appearance that everyone likes everyone else.
Northern Europeans, meanwhile, tend to prefer the "We're all adults here, so let's cut the bullshit and say exactly what we think." Being honest and genuine is more important than being liked.
This part, I find really significant: And hey, I don't actually think we've personally even had any problems. And I realize that you may react very strongly and get nervous about us having problems, but realistically, do you actually expect to like all the other kernel engineers? And equally importantly, not everybody has to like you, or necessarily think they have to be liked by you. OK?
That strikes me as a very Northern European view, that is not as likely to be shared by most Americans. It's just not how we're socialized in America. And too often, "professionalism" gets defined as "American style," while anything un-American is deemed unprofessional, which is not quite right.
The algorithm might be stupid, that doesn't make the person stupid. Ad hominem attacks are a very poor way to defend your point and will result in people not wanting to work with you.
Saying "grow a thicker skin" won't make it better either.
Linus is a brilliant engineer, his people skills not so brilliant. But we all knew that already.
The things Linus mentions are what happens as a result of supposed "professionalism".
People are emotional, reactionary creatures with very different needs.
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. As was shown on a recent post - Linus reverted to swearing in his native tongue because English wasn't sufficiently rude enough for him, and those who let the fuckup slip through all admitted their fault and identified that they would take steps to ensure it didn't happen again.