I would say this statement is a very clever move from GitHub side. I guess they have skilled PR people working on the issue.
At first look, the cited article seems to admit to everything. As a result, it will be sort of last news on the topic - if they admitted Horvath is right and they even put on leave a founder and the programmer and founder's wife will not be allowed to enter office, then what's more can be said or written? Github did everything it could to resolve the issue.
The point is that they did not admitted anything. The only paragraph that contains actual content is paragraph no 2., the rest is just speaking how Github grows and how they liked Horvath, how sad it is that Horvath is sad, etc.
So we have:
"We know we have to take action and have begun a full investigation. While that’s ongoing, and effective immediately, the relevant founder has been put on leave, as has the referenced GitHub engineer. The founder’s wife discussed in the media reports has never had hiring or firing power at GitHub and will no longer be permitted in the office."
So they have started "full investigation", just that. After two months when everybody will forget about the issue, the founder with his wife and the programmer might be back at Github (who knows what the investigation is going to prove - Horvath will not take part in it - she's no longer an employee). Whatever happens nobody will pay attention. No media will investigate the issue further because "Github admitted Horvath is right", so the topis is closed and no longer "hot".
I guess GitHub cannot publicly admit that Horvath is right or not, their lawyers would be mad, it is much better for them to keep all statements fuzzy and sounding good.
But I'm not convinced that this is a "clever PR move" as you suggest. What else can GitHub do at this point? Fire the people involved without even investigating?
Yes, perhaps they are bullshitting. But this is also what the PR release would say if they were trying to do the right things by all parties but don't have the information they need or the time they need to figure out exactly what the repercussions should be.
When the topic is as controversial as sexism in tech and the workplace. Or whatever the flashpoint happens to be at the moment. Like sequoia, I've noticed that controversial topics brings out the most incredible responses from both sides, and often with very little definitive evidence. To me, this is a sign of how deeply felt this topic is, and how much it is just under the surface of our thoughts, ready to explode when an appropriate trigger occurs.
I laughed when I read the quote above and thought it was a good comment.
In the case of GitHub specifically, the issue is even clearer. This is a company that for years had a blog with little else than their drinking escapades. Perhaps that's changed, but the burden of proof is on them.
The only thing that is up for dispute is whether this particular case is an example of sexism in tech or not. We can't be 100% sure, but at this time it's safer to assume that the weaker party is right, if only because the stronger party can handle a quick-to-judge public much more easily than the weaker party. I'm not saying it's boycott time, but it's best to at least open the discussion with that assumption in mind. Again, the burden of proof is on GitHub.
I can see how "to align with the weaker party" can be a sensible goal for a society. However, in this case it directly conflicts with the presumption of innocence principle, which is an even higher goal for a just society.
So no, the burden of proof lies in whoever is making the accusations, whatever the (un)balanced of power between parties is.
What we should do is (1) not judge any party until there are enough facts on the table (of which we don't have many right now); (2) strive for an impartial account of the events; (3) judge only on and after evidence has been collected. If you want to support a cause, pushing for people to follow this recipe would work much better than pushing for "the weaker party is right until the stronger party proves themselves".
Because sexism in tech is a fact, this occasion is an opportunity to discuss it. Debating whether Horvath is right or wrong is not only futile, but is also potentially harmful to her, and that harm is far greater than GitHub's. Presumption of innocence is only a principle in legal disputes, and this, currently, isn't one, nor are we the jury. There will be no great injustice done if the assumption turns out to be false, but there is a lot of harm being inflicted on Horvath right now by people equating her position with that of a rich company and suspending any form of judgment. This does not only harm her personally, but the entire industry by implying that sexism in tech is disputable and pending "further data", which it isn't.
Given that sexism in tech is real and serious, that GitHub has a bit of a spotty background on that issue, and that GitHub does not deny any of the allegations, this is a perfectly good time to assume something bad has happened and discuss measures to correct the situation in the industry. If it turns out GitHub has fallen victim to the very real injustice of sexism in tech, I won't shed a tear for them, but will be excited to see them face the challenge and lead the way forward.
The presumption of innocence doesn't mean that anyone must either think or pretend to think that someone is innocent, any more than freedom of speech means that facebook can't take your youtube link down.
This is a good illustration of the point in the grandparent comment. This is simply not true, and I can't even think of any fallacy/ belief/ blindspot that could be adopted by a somewhat rational listener to make it sound convincing. (just to address the recalcitrant credulous among you: consider whether there is discrimination against Down Syndrome sufferers amongst tenured faculty on math departments)
In topics where people have deep vested personal interest or emotional investment, the quality of arguments that they would view as convincing goes down (often way down). The tragedy here is that the discourse about complicated topics which are important is overrun by people who have either (or, most often both) vested interests in a particular outcome, or little knowledge about the topic.
Saying "period period" at the end, I think, indicates that on some level, the parent commenter knows that s/he is presenting a weak argument. The poster's emotion overpowers this, however.
QED
The reason I put "period" is because many people aren't aware of the current body of research in gender studies and sociology, and modern definitions of sexism (a simple introduction can be found here[1], esp. unintentional sexism: "The tendency to use intent, rather than result, to measure whether something was offensive and inappropriate, and therefore sexist, is tied into male privilege and the way that it enables sexist practices to be seen as normal."). If women are largely absent from a group wielding any social power, then by definition sexism exists (or sex-based discrimination, if you prefer), unless you can prove that being a woman is a relevant debilitating disability, which I don't even think anyone conjectures. Because the data suggests[2] that diversity in Silicon Valley is severely lacking, this is a serious problem in Silicon Valley.
(Any rationalization such as "but what if women don't want to be in tech" is irrelevant. The assumption is that all groups want to take part in powerful institutions, and if they don't, it must be because somewhere along the line society encouraged them not to want that, thus effectively removing them from power.)
[1]: http://finallyfeminism101.wordpress.com/2007/10/19/sexism-de...
[2]: http://money.cnn.com/2013/03/17/technology/diversity-silicon...
Another case in point, it was a counterexample, not a comparison.
In your case, I now believe you are primarily just a sloppy/ bad thinker (who is also heavily invested in a certain position), but my original point about emotion clouding judgement still stands.
And, again, I'm sorry for my sloppy thinking, but I believe that "consider whether there is discrimination against Down Syndrome sufferers amongst tenured faculty on math departments" is not a counterexample because pertinent disability most certainly doesn't fall under any definition of sexism/racism and other unfair discrimination (same goes for quadriplegics in the NBA). Pitting disability against sexism as a counterexample appeared to me to be a brow-raising comparison. This fallacy is called reductio ad absurdum or a straw man.
If you'd like, I can come up with a better counterpoint (or so it would seem to my feeble mind, which I actually had to exercise for this): white players in the NBA. However, that, too, would not fall under the modern definition for racism, as racism (like sexism) is "prejudice + power", and I don't think anyone suggests white men lack power or influence in American sports.
And if I was sloppy by not qualifying the term "a well defined group of people" to exclude disability, forgive me, I thought it was patently clear from the context, namely a discussion on women. And please don't try to counter with discrimination against those who don't know programming or village idiots, because the definition excludes that kind of "discrimination", too, and I hope that's clear enough without me quoting vast amounts of research verbatim.
3,000 us army deaths in Iraq, and of those, 2,938 were men, 62 were women.
You are correct, but only if the term 'discrimation' includes 'discrimination based on skill levels.' If not, then you are assuming that power-relevant skill is distributed evenly, which is baldly false in many real-wrld situations.
And you are absolutely right. Sex discrimination is systemic, probably starting in kindergarten and even at home. However, it's hard to fix education if young girls don't have lots of positive role-models to look up to, and you can't make those role models unless education is fixed. So fighting sexism has to be systemic as well, and at all levels at once.
It is telling that the topic of sexism in tech and the workplace is controversial at all.
Yes - it tells use that it's a deeply emotional and often deeply subjective topic where situations can be interpreted very differently depending on your point of view and you do not necessarily have as clear a villain and victim as people like to have.
I'm not sure if you were framing this as a net negative or positive, but I actually do appreciate when these controversial debates occur. I like to see all the contrasting world-views brought out into the open and into conflict with each other. I agree that civility is a problem, though.
Anyway, I mention this because I worry sometimes that HN's "flamewar detector" (or is it purely flagging?) seems to kill these kinds of threads, ones with a high comment-to-upvote ratio (though some notable recent threads have seemed to escape this). I often wonder if this mechanism is worth the trouble. I suppose if heated debate leads to polarization of opinion, that's an issue, but I don't know if that's necessarily the case.
I can reassure you that this thread would have quickly been flagged off just a few months ago.
I'm guessing it's due to the fair amount of criticism PG received (from myself included) over how the flamewar-filter censored sensitive, yet important, discussions just like the ones this story sparked.
Or, the complaints including yours probably did have -some- influence, but I think you're overestimating how much because to you, your comments were a heartfelt effort to make a point, whereas to pg they were 'add one to number of complaints of type X'. It's still important, given said number will have been factored into the decision making process, but probably not that important.
Regardless; I can confirm that many people complained about it and roughly a week or two after the whole 'PG is a sexist' kerfluffle sexism related threads stopped being flagged off the frontpage... It seemed like relevant information for the OP.
It definitely leads to my polarization, along with other (seemingly unfair) events in my life. Plus, it is hard to express any other opinion than in favour of the women, which leads to unvoiced discomfort and is clearly not the situation you want in an industry.
I wish women would speak up more often for men's cause. That's also what equality means.
If they are starting now to investigate, it means that when troubles were occuring, or even when Julia H. gave her demission, they didn't care enough to investigate thoroughly (perhaps they have other priorities, that's just a fact).
This in itself is not good looking, and I feel that from there whatever really happened, they won't have the full version anymore (one of the party is already out) and they will have a huge incentive to go into damage control mode instead of genuinely trying to make the situation better for both parties. Especially, the more they do, the worse their image would be on the PR front ( I hope they do whatever is fair anyway, but the balance is tipped).
I admit, I do care about things more than most. My workgroup, and much of the company I work for migrated to github enterprise (and a lot in github public) about a year ago. These kinds of things sour opinion. There are differences between a single bad actor/incident and a systemic problem in a toxic workplace. We don't really know what this is, but it was clearly more than at least one person was willing to put up with.
It's bound to be difficult working in an environment where 4:5 of your peers are the other gender. I worked in a couple of workplaces when I was younger where I was the only male. It was rather eye opening and sometimes uncomfortable to say the least.
Also, people might forget about the issue in 6 months, but the bad taste in the mouth we have now will stay attached to the brand. The best move IMO would be to come 'clean' as soon as possible, and let the hype die down from there, provided they are OK with doing the right thing, whatever it might be.
GitHub's response neither confirms nor denies any part of the story. It does say the founder's wife will no longer be allowed in the office, but that is not an admission of wrongdoing nor of her ever having been in the office.
Edit: The only thing this response proves is that GitHub is taking these allegations seriously, which hopefully means there will be more information after they have time to investigate. Try not to jump to the many other conclusions already posted in HN comments.
First hand testimony might be imperfect, but It is evidence.
Whether or not its conclusive remains to be seen.
That's the larger point.
Certainly, the above linked article lends at least some credibility to some claims.
The fact that the wife of a founder needed to <even be mentioned> in this type of PR damage controll manouvre...is a huge red flag by itself.
Please, stop speculating. Have patience, wait for actual information.
Well, they do say:
We know we have to take action and have begun a full
investigation. While that’s ongoing, and effective
immediately, the relevant founder has been put on leave,
as has the referenced GitHub engineer. The founder’s wife
discussed in the media reports has never had hiring or
firing power at GitHub and will no longer be permitted in
the office.
So it's not like they're completely silent. They said both the referenced founder and employee have been put on leave and the wife, who apparently was allowed in the office before this, is no longer. They didn't flat-out admit to anything, but it's not like they're totally silent."While that’s ongoing, and effective immediately, the relevant founder has been put on leave, as has the referenced GitHub engineer." == "We don't know what to do yet but we're trying to prevent variables from changing"
"The founder’s wife discussed in the media reports has never had hiring or firing power at GitHub and will no longer be permitted in the office." == "If she said anything along those lines, she had no authority to do so, and misrepresented herself and her role at GitHub"
Yes, it's legalese, but it's not actually saying or admitting anything that anybody didn't already know. It's filling the silence that would otherwise breed directionless slander and conspiracy.
It's manipulative, but arguably well intentioned, and can possibly lead to a more constructive outcome than the free-form slather that would have occurred in a communication vacuum.
In both cases, they wouldn't want him having any potential influence on the investigation. To do that, his power within the company needs to be suspended until a conclusion is reached. The parties investigating (likely HR and the other founders) must be able to do their job without fear of retaliation from the accused founder, that would taint the decision.
Of course it can also mean the opposite - my point is merely that suspending someone pending investigation says nothing at all about guilt.
I'm seeing plenty of mea culpa in this, and that's good. They could have responded far worse, and only slightly better.
> It's unfortunate TechCrunch and Valley Wag posted the story without first corroborating at least some piece of it.
I think we have to be careful with statements like this. Yes, they could have tried to find a Github employee who would corroborate part of it, perhaps the assertion that the wife was in the office periodically. But the problem with that is that it is perfectly reasonable to think they would have failed to find anyone willing to talk about it. Then what? Should they not publish? If they hadn't, would Github be investigating now? Would anyone be on leave? Probably not.Asking for corroboration is fine, but we should be mindful that some things that are true can't be corroborated and demanding corroboration just gives the accused party the de facto ability to suppress the information or the debate.
Her story passes a basic smell test, it very well could be true, and there is no specific reason to doubt her. While this doesn't mean it is true, it isn't necessarily irresponsible to publish it either.
Again, that is speculation. "What ifs" are not useful here.
As "news" outlets, I expect both sites to corroborate stories before posting them. If they don't, they are effectively tabloids. Posting allegations like this is the definition of tabloid journalism.
There are too many people involved in this story for me to believe that zero of them were reachable for comment. TechCrunch only vaguely mentions "awaiting comment from GitHub", which could mean anything.
I do think it is irresponsible to publish such a story without any corroboration because it implicates several people directly and an entire company's work environment with nothing more than one person's word.
The whole story could be true, but the fact is no one knows; TechCrunch and Valley Wag certainly don't.
We only have the luxury of observing one "version" of events (unless you can hop between multiverses). Therefore, the only way we have to evaluate past events is by asking "what if" questions.
What if TechCrunch hadn't picked up the story? Basically no one would have heard about it and Github quite possibly wouldn't have felt the need to respond or investigate (maybe they still would have, another "what if", but they wouldn't have been under as much pressure).
Something went down. I'm not saying we should just lynch the accused parties and move on. But I am saying that often the only way for a small actor to get attention is for a news outlet to pick up his or her story. And if they refuse to publish without some kind of official confirmation, then very few such stories will be printed, because the larger, more powerful entity will quash them with silence.
Classic case of confirmation bias.
Would you accuse scientists of confirmation bias if they chose to look for more evidence rather than just publish the results of the first experiment?
Comment three was 'aha they issued a vague apology, this is basically a FULL ADMISSION that everything Horvath said was true!'
People: when did our brains melt and spill out of our ears? There is not enough public information present to reliably prove or disprove anything at this point; Github issued a nonspecific semi-apology (to wit: "It’s certain that there were things we could have done differently" well, yeah this is usually the case) with some promising indications that they are taking the issue seriously & looking into it.
Now we wait. Stop saying github is admitting to every point of Horvath's assertions! Stop saying Horvath is a liar! You don't know these things! Take deep breaths, listen for a bit, and wait for more information to come out.