Re:Google's Civil War
by wswkb on Sunday May 19, 2019 @12:13PM
(#19954009)
I should be able to put, say, "this method is fucking up that variable" in a code comment without a puritan telling me not to do so. Which is funny, as it shows that we're going full circle.
[ Parent
| on HN ]
Personally, I'd prefer "fucking up" to go away, along with "rape" as a colorful equivalent of ruining/causing damage to someone or something.
It associates sex with violence and destruction.
A similar thing used to happen with "gay", which kids would use as an adjective for frustrating or annoying situations.
My preferences notwithstanding, it's still better to be clearer about what's happening. "Fucking up that variable" says very little about the cause of the problem, and its possible solution.
Personally I'd prefer to work in a company where basic elements of the English language aren't policed with authoritarian fervor and would seek out alternatives ASAFP.
Re:Google's Civil War
by skinnymuch on Monday May 20, 2019 @12:44AM
(#19957587)
What does fucking up have to do with sex? I’d imagine it’s used in a sexual context in a significant minority of the time. And that’s not what it’s associated with.
When I think of something being "fucked up", the last thing I think about is sex. Those words have grown a meaning of their own, away from the one they had.
Why? Are you asking to be able to swear in front of clients too? Because the code isn't guaranteed to stay in front of favourable eyes forever.
If you think that's bad, wait until you see how nit-picky people get in code reviews. I wouldn't be surprised if there were lint rules for swear words.
If you can't deal with criticism of your code, maybe working at a big tech firm isn't for you?
Re:Google's Civil War
by AndrewDucker on Sunday May 19, 2019 @01:05PM
(#19954258)
If you can't criticise people's code without swearing maybe working on a professional environment isn't for you?