Slashdot Mirror
Developer Misinterprets Linux Code of Conduct, Suggests Replacing F-Word with 'Hug' (neowin.net)
Seeking compliance with Linux's new Code of Conduct, Intel software engineer Jarkko Sakkinen recently requested comments on a set of changes to kernel code comments which Neowin described as "replacing the F-word with 'hug'. "
80 comments quickly followed on the Linux Kernel Maintainer's List: Several contributors responded to the alterations calling them insane. One wondered if Sakkinen was just trying to make a joke, and another called it censorship and said he'd refuse to apply any sort of patches like this to the code he's in charge of...
Some of the post-change comments read "Some Athlon laptops have really hugged PST tables", "If you don't see why, please stay the hug away from my code", and "Only Sun can take such nice parts and hug up the programming interface".
Eventually LWN.net publisher Jonathan Corbet deflated most of the controversy by pointing out that Linux's new Code of Conduct applies to future comments but clearly indicates that it does not apply explicitly to past comments.
And Jarkko Sakkinen acknowledged that he had missed that part of the discussion.
80 comments quickly followed on the Linux Kernel Maintainer's List: Several contributors responded to the alterations calling them insane. One wondered if Sakkinen was just trying to make a joke, and another called it censorship and said he'd refuse to apply any sort of patches like this to the code he's in charge of...
Some of the post-change comments read "Some Athlon laptops have really hugged PST tables", "If you don't see why, please stay the hug away from my code", and "Only Sun can take such nice parts and hug up the programming interface".
Eventually LWN.net publisher Jonathan Corbet deflated most of the controversy by pointing out that Linux's new Code of Conduct applies to future comments but clearly indicates that it does not apply explicitly to past comments.
And Jarkko Sakkinen acknowledged that he had missed that part of the discussion.
It's the intent behind it that matters.
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
Just last night I had a nightmare where I had to submit to the SJW thoughtpolice agenda or get shunned out of my programming group. It was straight out of 1984. That's exactly where this is heading. Fuck your feelings. Stop this Code of Conduct nonsense now.
I'm glad to see that the code of conduct is resulting such good use of developer time.
These sad, sad people clearly need a hug.
You can bloody well go fuck yourself for trying to equate colorful language with racist speech.
You must be pretty damn sanctimonious to have never used "fuck" or any other language someone else might find objectionable in a professional setting. Maybe you have the benefit of only working with individuals just as or more competent than yourself, but there are some people who need to be told to stay the fuck away from something, or they will fuck it up and make a real fucking mess of things.
Myself, I'd rather be told to "fuck off" if I need to be. If I think it's out of line, I'll let you know. If I think you're being an abusive asshole, I'll let you know that too. Otherwise I'd rather not sit through some milquetoast discussion where it feels like someone is trying to address a five year old child that shouldn't hear the bad words. Frankly, that's more dehumanizing than someone being pissed off.
It's a good idea to treat people with respect.
But saying a piece of hardware fucked up some table is not attacking a person. We're going too far with the SJW speech-police. Sometimes it's necessary to make a point strongly.
If you want equal rights, that means you don't get to demand special protections for your feelings. Equal means equal: you should be adult enough to accept that the real world has some level of swearing in it.
This kind of thing is a cancer and will spread if it isn't carved out. Eventually we'll be more focused on policing speech than on technology. It will not end well.
That's why these kinds of exercises always end up in disaster. If your rule is any more complex than "Nobody shall prohibit anyone their natural rights to freedom of speech" it ALWAYS ends up being initially misinterpreted, and later abused by those in power.
Custom electronics and digital signage for your business: www.evcircuits.com
If you're not intelligent enough to see the message instead of being focused on their particular vernacular, then you do not qualify for the project. Your inability to see past transport protocol Prejudice in verbal communication shows a certain lack of perspective and maturity necessary 2 a technical project
Why do you assume that anyone who would say "stay the fuck away from my code" must be a male? Is it not possible for a female programmer to say that? Would that be toxic femininity?
It's hard to keep track of all these bigoted memes the Left invents each day to signal how non-bigoted they are.
I've fired nice polite people for being fucking incompetent air thieves.
I've left threats of physical violence in comments, for good reason. If you'd cleaned up _that_ block of code you would too.
I don't 'act' professional, I am professional.
John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
Bullshit, we don't hate female coders, we hate having incompetent coders on our team.
Good female coders also hate fixing incompetents shit, can and do cuss like sailors.
How do you tell someone's sex over the internet anyhow? rChromosomeTest.exe?
John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
This argument comes up in any discussion about what language we should use. The choice of language is somewhat secondary; what really matters is the exact meaning of the word "should" in that sentence. Or rather: what the consequences are of using the wrong language - in any situation. Most people would agree that it's better not to use swear words or insults, but what happens if someone does? Being told off for bad manners, having bad words censored, seeing your pull request denied or your paper rejected, public shaming, being ostracized from the community, fired, or even prosecuted in court? When people talk about acceptable language in their communities these days, the full range of those consequences will be openly discussed and often seriously considered.
It's good to have a code of conduct - written or unwritten - in any community, but when transgressions carry serious consequences, you'll invariably see some perverted snowflakes push the boundaries of what's acceptable, and gleefully call out violators, especially those with opposing viewpoints. Can't say fuck anymore. Or black. Or master / slave. Peek and poke? Nope. Male / female connectors are out. Can't insult anyone or anything... and you violate that rule whenever someone, anyone feels insulted. Or just crabby.
Codes of conduct regarding acceptable language are best left unwritten, and are certainly best left undiscussed at length. Because the more you discuss them, the more you formalize them, the worse they get.
If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
Actually, there is a direct and strong correlation between race and violent crime which persists across all class strata.
In addition, rich black people are even more likely to commit violent crimes compared to rich white people than poor blacks versus poor whites.
The more rich blacks are, the more violent they become, per capita.
That's saying a lot, too, because they are 17 times more likely to commit violent crimes than white people.
Enjoy further reading, which has been suppressed by Google.
http://www.bjs.gov/content/pub/pdf/htus8008.pdf
http://www.fbi.gov/stats-services/crimestats
If you are so immature that other words can't fulfil your need to express displeasure about some work, I feel sorry for you, your friends, and your family.
Would you say it to your 6 yr old daughter?
Swearing is stupid, but Your deep seated need to control others speech patterns is silly.
And no - I wouldn't say fuck or whatever word triggers you in front of a child, or my mother, or Jeebuz either. I have a magic ability to tailor my speech to the group I'm with.
The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
You must be pretty damn sanctimonious to have never used "fuck" or any other language someone else might find objectionable in a professional setting.
That's quite a shifted goalpost. "Fuck or any other language someone else might find objectionable".
For what it's worth, I've never used "fuck" in 7 post-grad years in academia nor my 14 years in the software industry, and nor have I heard the word used in a way that was directed at a current or former colleague, nor at their work. I've worked with plenty people smarter than me and less smart, and plenty people more industrious than me and less industrious.
(per the terms of your shifted goalpost, there have been in that time lots of words that someone else might find objectionable, but that's such a watered-down goalpost that it's meaningless).
If someone needs to stay away from something, I normally say something like "Jones, I don't want you to work on this" or "Jones, don't work on this". The word fuck isn't needed to make my instruction stronger, and indeed wouldn't make it stronger.
If someone has made a mess of things in the past, I've said stuff like "the architecture for this model wasn't suited to the use-cases, and it'll require a ground-up rewrite, otherwise we'll face risks XYZ". Phrasing it as you suggested "fucked up and made a real fucking mess of things" isn't as actionable, wouldn't be as respected by management, and I'm having a hard time believing it would deliver results as well.
I'd rather not sit through some milquetoast discussion
None of what I've said is milquetoast. It's more directed and actionable that your suggested fuck phrasing, and it's effective at getting results.