Why You Should Spend More Time Thinking About github admits significant mistakes were employee
I had a few questions about what is the proper way to handle these tickets. Some are due to errors in the application process and some are due to mistakes at the company level.
The github service says that all tickets are investigated, but I find it hard to believe that they’d have this many tickets when they have so many serious errors. I’ve seen many tickets that were clearly invalid and they are still pending. I also found it hard to believe that the engineers who created the tickets are the ones to have made them. A few months ago, they were probably just making a mistake.
The github service says that it will investigate these tickets and get them resolved if they are indeed invalid–but I think that is a really big stretch. They are clearly not going through the trouble of going to the actual engineers who created the tickets. It’s not like the service is going to check and see if the ticket was written by a real person. If they have to check at all, the system seems to be designed to check for invalid tickets, not real ones.
It’s a little hard to tell that Github is doing anything this time, but it’s not hard to know that it’s not. Github is a popular and widely used service that is often used for bug tracking and bug fixing. Even if Github’s engineers are incompetent, it’s still a pretty big deal that they created tickets like this and it affects the entire service.
I don’t know whether I’d want a ticket like this, but I wouldn’t be shocked if Github is at fault here. Github’s service is a popular and hugely used one that makes it easy for developers to quickly get their code into production. The whole point of Github is that it is free. If Github is now liable, then this is a big deal, because the site itself is a huge source of revenue for Github and its investors.
One of the most annoying things about this situation is that Github users have every right to believe it was a mistake. The company has to pay for what it did, they probably deserve compensation. But if any employee had done such a horrible thing as this, Github could have made the situation much worse, for everybody else. Github could have spent far more time on fixing things, and that would have meant a few more thousand $$$ of lost revenue.
This reminds me of the infamous “diversity-violation” issue that happened at the Facebook, Twitter, and more. Facebook was criticized for a few reasons: one, the company had a large number of white people in its workforce. Two, the company failed to hire a black employee. Now, I’m not saying that Github made this mistake, but I don’t think it’s fair to blame the company for it and say that they deserve compensation.
It gets worse because this isnt exactly the first time something like this has happened. There have been two other instances where Github has admitted that their employees committed some type of discrimination. Both incidents were caught by internal investigations. One incident involved a white woman working as a software engineer, the other was a white woman who was hired as a software engineer but was fired after she complained about racism.
Github has taken these problems much more seriously in the past, so in this case they clearly think there is a problem and want to fix it. That’s a good thing, because it means that many of the problems that our company faces will be fixed before it’s too late to do anything about them. This is a good thing to hear, because it also serves as a reminder to us that there is a cost associated with any type of discrimination that we see in the world.
One of the reasons this whole case has been such a mess was because of github’s decision to hire a woman as a full time employee. She apparently had a hard time with the sexist language she was exposed to and had to be fired. She is now suing Github for $4 million because of the way she was treated. She has filed a lawsuit against Github so if you ask her anything about that incident you’ll get nothing but her angry tone.