"You have a hostile work environment."
is
"We don't have a provably illegal hostile work environment."
then that doesn't inspire great confidence when evaluating it as a place to work.
I did. So far it's working out in GitHub's favour. But maybe I missed something, so do your own research.
I would think, however, that any sort of reasonable minority calling it a "hostile work environment" would indicate a problem.
I think this can have positive outcomes for GitHub, if they allow it. And if Julie does. Right now we're just in the "public fighting" phase.
That probably says more about the mythological status they had before than about the reality now, but it of course will have an impact on their ability to hire though.
It also should have, and it's normal, and it's how startups turn into big-corps, and that's just the way things are.
The sad truth about culture is that a sustainable culture will feel much more like your parents home than your college dorm; and that will never change... because it's a good thing.
That is the single best line I've read about work culture in software companies in......ever.
I read Github's statement as: "We don't really have any evidence of anything, so we're not going to say anything because we might get sued by one of the involved parties." That situation isn't a good one to be in (and letting an organization get into that situation is serious negligence on the part of leadership).
I'm skeptical. The fact that there is a documented procedure isn't nothing, but it's not that much more than that. I suspect if I went back and counted, a strong plurality of the "I worked in a hostile male environment" accounts I've read occurred in companies with HR departments and explicit sexual harassment policies- GitHub was pretty unique. I've worked in ten-person companies with an HR person.
What an HR department does is make sure management doesn't get sued. The culture of the company isn't something they can control by fiat.
GitHub isn't denying that there were problems and isn't claiming that her story is a complete fabrication. They merely said they don't believe they will lose a lawsuit over it. If anything, they validated that her opinion was fair
That's a good point, though: from our perspective it is still just he-said/she-said (er, she-said/she-said), and I guess it will always be. I guess it just depends on who we (individually) feel is more credible.
Based on Hovarth's public behavior, I'm not feeling too great about her story...
My first comment was in response to onewaystreet's comment "At every company in the world you can find at least one person who hates their job or has problems with their coworkers. I'm not sure they are the person you go to for a fair opinion." The statement seems to imply that it was sour grapes and not an actual systemic problem that led to this situation. My response was that Github's official response admitted that there were problems (explicitly, mind you) but they believed they would win a legal case if it came to it.
My second comment was in response to kelnos's comment 'If you read Theresa Preston-Werner's post (linked above), she claims that the "mistakes and errors of judgment" were completely unrelated to the harassment story, but were discovered during the harassment investigation.' That comment gave Theresa's story much more credibility than Horvath's. Now, this would be a standard he-said-she-said were it not for the fact that Github's reply doesn't refute Horvath's allegations. In fact, Github's reply implicitly refutes Theresa's claim: after all, if what she were saying is true, the official response would have made it clear that the investigation uncovered issues unrelated to the situation at hand.
That is not obvious, and I think it is impossible for us to figure out why the PR agency/HR/management/investors/lawyers that crafted this statement was not more specific and what it means that they did not say something. Only reading the report itself or getting a full summary of it can help with that.
IMO what it means is that people should work extra hard not to contribute to a hostile work environment, or expect to be perceived as contributing to a hostile work environment at randomly unpredictable points in their lifetime.
Shit does happen, regardless of the majority of one's coworkers best intentions.
Every work environment has hostilities. The only way they each differ is in who is the recipient of the hostilities, the degree of hostility present and if that hostility is illegal or not.
In that sense, the statement "We don't have a provably illegal hostile work environment" means exactly nothing, making Github no different than all the other workplaces you are evaluating.
There are three sides to every side of a story... TPW's side, JAH's side and the facts. Given that all we really know are TPW's side and JAH's side and that we have no real facts beyond admitted errors in judgement, we really have no more information upon which to base judgement than before. I know of no company in the world provably immune from errors in judgement, do you?
In other words, you and everyone else should evaluate github based on everything else you know about github and completely discount this entire debacle, since it has not shed light on anything that isn't as equally possible at every other company you may be considering.
That strikes me like saying that all sex is rape, it's just a matter of how violent or unwilling.
* reductio ad absurdam
* red herring
* strawman
* non sequiter
Not disagreeing with you, just raising a point.
http://en.wikipedia.org/wiki/Intuitionistic_logic
Incidentally (a further parallel to the Axiom of Choice) Intuitionist Logic is also referred to as Constructive Logic.
http://en.wikipedia.org/wiki/Constructivist_mathematics
One branch of constructivist mathematics eschews the axiom of choice, and all do not allow proof of existence by RAA on non-existence.
This is dangerous logic. The court of public opinion is a feedback loop. If an unconfirmed accusation gets no traction then the most hardcore wrongdoers will escape justice because everyone is too afraid to come forward. At the same time, if a confirmed accusation goes unquestioned then someone who has made a false or exaggerated accusation has a huge incentive to cajole friends into making confirmations that are also false or exaggerated, and the more false accusations are made the easier it is for the original accuser (or the likes of Nancy Grace) to convince others to make further false accusations.
That's why these issues are so contentious. Getting to the real truth is practically impossible because people form an opinion first and then produce evidence that comports with it, and that misleading evidence influences the opinions of others who do the same thing until the truth and the story have no relation to each other.
It's an issue where you have to choose between punishing a lot of innocent people (and increasing the power and thereby occurrence of false accusations) or allowing a lot of guilty people to escape punishment. There isn't a good answer, and that makes people angry -- especially if you're one of the innocent people who was punished or one of the victims of the guilty people who weren't.
If this whole thing were as bad as JAH has made it out to be, I would have imagined we would have already seen damning emails and other written correspondence backing up here allegations. As a company that doesn't most of its work asynchronously through written prose, it's not like github doesn't have oodles and oodles of written correspondence that would support her position better. There's email, pull requests, chat, etc. Given the duration of employment, she must have plenty of things to point at. If she didn't she should have made sure that some of the offending interactions were captured in written form at least once.
It probably will challenge their recruitment of women though.
The answers to these questions are still true today:
* does github make a great product? yes. * does their product make software development and open-source better? yes * are there interesting problems to work on there? yes. * would I be working with very talented people there? yes. * based on what we know as facts or admitted to as facts, would taking a job at github subject me or people I care about to these injustices? AFAICT that's no more likely than at any other company comparable to github in terms of the benefits of working there. Anyone working at github is there at will. If they feel wronged, they can leave, which means I don't have to worry about people I care about being wronged.
The only way my mind would change on this is if I see a voluntary exodus of talent from github over what happened. Absent talent leaving in the current hiring market, we can only come to the conclusion that these wrongdoings were isolated and personal.
Let's keep an eye out for who has left since March 15th, 2014 or so and leaves over the next 3 months. Of that cohort, discount TPW, JAH and anyone who leaves to join TPW's new venture. With the remaining figures, then check if that churn rate for github is any higher than it would have been had this event never happened. If it is not, then this whole issue is pretty much irrelevant.
They're hiring new HR people, GOOD. They're adding training for employees (probably much to the annoyance of those employees), good.
These means that it'll be easier to make the places safer and better for everyone. That's what I'd look at.
Interestingly enough, I'd say that smaller startups suffer from larger biases. Basically if the founders don't like you for some reason or another, you're in for shit. If a "CTO" who worked at the company since the beginning doesn't like you, you're fucked as well. And there's no HR to turn to.
However, determining how people will decide when put to such a situation is difficult. Speaking personally, I would certainly be wary, but I'm not going to dismiss a potential employer outright over something I don't have the complete facts about over one story.
Followup: that statistic is 75% made-up.
Human interaction is not black and white (don't read into that). While this situation will never be totally transparent to the vast majority of us, the necessity of working within our limited knowledge does not imply our knowledge should necessarily be limited.