Hacker News new | past | comments | ask | show | jobs | submit login

And? Blaming everyone for "double speak" is rather counter-productive and a great way to destroy the discussion, as it ignores some people are actually interested in a honest discussion. What a wonderful way to create toxic environment ...

Having an open discussion means you accept that other participants may have very different opinions, and agree that honest fact-based discussion is the correct solution.




No. If you want to suggest cutting down on something, suggest cutting down on it. Don't wrap it up on weasel words that never actually say "cut down on it". Governments, management, etc, are well-known for this tactic - they'll say "we're going to review this policy", and the next thing you know it's been diced to shreds, but the politicians/management involved never actually outright said "we're ending this policy" so they get off without apparently having ever said anything to alienate anyone.


The fact that group X is known to use certain tactic does not mean Y is using it too.

In any case, screaming "WE'RE NOT EVEN DISCUSSING THAT!" and calling for getting the person fired is hardly a proper response. What I'd like to see is a fact-based response to the memo, showing numbers/reasoning for the individual policies, etc.

My main take away is you really can't openly discuss this topic (not just in Google), which was one of the points. Ironic.


The story is currently at "1600 points by QUFB 14 hours ago | 2129 comments" so your take away that you can't discuss this topic is indeed ironic.


The primary place where the policies should be discussed is the company. He got fired for sharing his opinions. I don't see how is that supporting open discussion of the topic?


> The fact that group X is known to use certain tactic does not mean Y is using it too.

No, the use of English in politics (which this is) is pretty consistent, actually, in my experience. If he wanted to have a discussion, point at a policy and suggest an alternative rather than falling back on "merit is good, women are terrible engineers".

Replacing discriminatory hiring with paid apprenticeships and other education for groups the organisation is lacking in, would be a great example. Men can still get into Google because there's more of them in the pool. They're never discriminated against for a job, since the apprenticeship pool is separate from the job pool. Google gets a more-qualified, more-diverse workplace with more control over its training program. A win for everybody.


Firstly, I'm not a native speaker and I don't dare to judge how consistently is English used in politics. But once again, I claim that making conclusions merely based on "language similarity" or something like that is a poor way to discuss stuff.

Secondly, I find it perfectly valid to discuss the very foundation of the policies (instead of discussing individual policies).

FWIW this does not mean I agree with the memo. But I think the immediate calls for getting the guy fired (and firing him) are damaging for the discussion.


So you're saying that discussing something, a discussion which can lead to cutting it down if deemed appropriate, is never a good thing? The way I see it, you're effectively rallying against a closer examination of a system regardless of whether it's a system that benefits or hinders the environment it exists in.

I hope you'll forgive me for saying it but that is my definition of the "burying your head in the sand" expression.

edit: furthermore, what if he's in fact saying that he wants them to be cut down? Why isn't that a reasonable motive to want something to be more closely examined?


If you're coming to the table with the pre-conceived notion that the program is bad and needs to be shut down without adequate replacement, then that's not in good faith. I'm responding to the idea that this person is, somehow, wanting a good-faith discussion - he's not, he has a specific goal of shutting down the program.

If people would like to discuss this, they can at least discuss it for what it is - an attack on the program. Treat it as such. Don't hide behind "he just wants to talk".

There are, no doubt, many people who discuss Google's diversity programs every day on a good-faith basis. They don't need a manifesto in order to do so.


It seems that it is you who is coming to the table with the pre-conceived notion that the program is an absolute good and that the letter is an absolute bad.


I read the letter. It has some very good points - many of which feminists have been pointing out for ages, to the surprise of nobody who's actually been listening to feminists. It also has some terrible points, and uses a severe misunderstanding of gender to attack women who work for or intend to work for Google. The decent points it does make are mostly an aside to the main point, which is that the author has a very strong belief that diversity programs are inherently bad and that women are biologically weak engineers.


I added an edit later, I assume it was after you replied so I'll ask again:

What's the problem of wanting some light shed on a program because someone openly believes it should be shut down? They're not doing an executive decision to shut it down without allowing for discussion, which is exactly what Google management is doing. He posted an opinion, partially based on facts and partially based on conjecture to bring attention to it.

In short: there's nothing wrong with wanting a program to be shut down and using that as motivation to put it in the spotlight. I don't see how motivations should get in the way of discussion and examination of existing systems; a system that is beneficial to it's environment should be able to stand on its own merits.

ugh, my "in short" is as long as its preceding paragraph :(


Generally speaking, actually, the vast majority of systems are fragile enough to fail to stand up to consistent attack. I don't subscribe at all to your belief that a good system can never be successfully attacked.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: