By all indications, Uber has a toxic work culture that costs them both top talent and organizational velocity.
I'm a college senior at a well-regarded engineering school. My CS classmates - especially women - simply do not apply to Uber, in large part because of its reputation for internal misogyny and general assholery. Four classmates interned there last summer, and as far as I know none are interested in returning. A friend of mine was actually warned off by her software engineer father. I've heard stories from friends who've worked there that corroborate Susan's tales of infighting teams and inexplicable reorganizations due to high-level backstabbing. The one woman I know who works there wants out. Susan is a high-profile and credible source; hopefully her post takes Uber's work culture issues from "open secret" to "problem that has public consequences for the company".
The CEO should crack down and take serious steps towards addressing this problem - not just for PR, but because his company is seriously suffering as a result of these issues. Unfortunately for Uber, from what I've heard, Travis is part of the problem as far as Game-of-Thrones internal politics and backstabbing goes. His "move fast and break things" persona sounds like a poor model for subordinates. Between that and the company's relative external success, I wouldn't hold my breath waiting for anything internal to get better any time soon.
Until it does, I simply hope that my acquaintances at Uber find somewhere less shitty to work.
Hijacking this top comment to provide some personal experiences.
I started as an engineer in the spring of 2014 and this was definitely the case there.
Top engineers were being poached from Google/FB and these people were trying to carve out territory in a quickly growing engineering team.
The misogynistic culture, in my mind, comes from most of the early employees being former frat bros. Culture was extremely heavy on the drinking; see "Work-cations" where most of the team would go to an exotic location which was half-hackathon/half boozefest. There were happy hours every week with open bar because all new employees would be flown to SF (no matter where home office was) for orientation.
Crazy, most ex-employees (even the early ones) acknowledge that the culture is bad but they got their $$$ so they won't have to work again for a long time, if ever.
> Top engineers were being poached from Google/FB and these people
> were trying to carve out territory in a quickly growing engineering
> team.
It is always a bit sad when one of the top characteristic of an engineer from organization X is their political ability to carve out an empire.
I'm a bit surprised she doesn't have at least one law firm trying to get her to be the lead claimant in a class action lawsuit. Seems like she did everything right and has a pretty sold case. Of course she may have signed that option away when she left.
Also, in California at least, your employer has to give you your full personnel record if you request it. She might ask them to do that.
I'm a bit surprised so many people want to give her advice. She's already taken a really bold step and written cogently and in a balanced way about her situation, the toxic culture at Uber, and made it clear she's moved on to a better place. Why talk about what she should be doing and hasn't done as if there is only one way to resolve this? Why not give thanks to the writer for writing this and putting up with all the drama it will cause in the hope of a better world.
Why not talk about how wrong Uber was in every way and at every level - allowing a manager to attempt to proposition new direct reports for sex on their first day, not immediately firing them for this, trying to suppress this when taken to HR, rewarding the perpetrator, killing her career there for vague reasons, let alone all the other dysfunction she mentioned in passing? Even just one of those points means a really toxic culture. There are little bits of men's behaviour in every large organisation which resemble this, why not talk about that and ways to make this better? There are so many ways this story can inspire us to do better.
I think you have incorrectly attributed ChuckMcM's comment as advice. He was just musing about his surprise that a law firm hasn't already contacted her considering the strength of her case, and having a thought experiment about the outcome.
In this case, it would greatly benefit the public good to litigate. Unfortunately, the risk of lawsuits is the single greatest motivator for U.S. companies to combat sexism and harassment in the workplace. We would hope that companies would recognize the inherent value of encouraging the growth of a class of employees so they can be productive, but this isn't the case in most U.S. companies.
I think it's unlikely that Susan would choose to litigate. She is motivated to design systems, write books, and advance infrastructure engineering. Her personal gain from a lawsuit would be slim (what would the damages even be? She probably has no employment gap, considering her excellent reputation in engineering).
I'm not a lawyer but I imagine in this case the damages would be puntive. It's less about how she was harmed and more about the fact that the company has rampant sexual harassment and a history of not handling complaints properly. A good way to teach them (and others who are contemplating doing the same) a lesson is to make them pay an outrageous amount of money.
Not saying Susan should be the one to sue them, but someone certainly should. Along with the bad publicity one or more lawsuits would definitely get them to clean up their HR practices.
The discussion here really highlights how people combine what they are reading with what they are thinking into a combined message.
I was reading her account and the GP comment from the uber throwaway and making observational comments about people who spend time on political maneuver versus doing excellent work. I've known a number people over my career who got promoted often and achieved great "success" but did so by manipulating the organization and not by doing anything particular noteworthy.
In my experience, that sort of behavior can really only be stopped top->down. There isn't any way that I have found to help someone see that they are incorrectly evaluating employee contribution from a position below there grade level. And like the author found, if the bad behavior continues above your manager, then that is a level of brokenness you can't fix. And as you point out she got out and was moved on.
I also phrased it as an observation, but I am sure that on reading her account there may be lawyers looking for a big payday (Uber is vulnerable) who will approach her. It's what lawyers do. Generally more established companies have a tighter rein on their illegal management practices to make it harder on the lawyers :-)
Uber was wrong, on every level, and that was status quo. And the cost of naming that wrong and speaking of it is high. It is sad that they are not unique in that wrongness.
There is only one way to make this better, and that is to tie this sort of behavior to a loss of money. There are many things we might advocate which impact Uber financially; One is to sue them, One is to give witness to their wrongness so that others will not work there, One is to boycott them as a customer or driver.
Sadly, there is no way to "fix" them because this appears to be cultural. That is the worst part for me, knowing about the rottenness in a company, knowing it "could" be addressed by a strong leader providing incentives for good behavior and disincentives for bad behavior, and knowing that no fixing will happen. That said if their competitors have a stronger (and better) culture, then they will be able to attract top talent in the space and dominate the market. We'll see if that works in this case.
Thanks for this comment - I agree with your points here. It is worth us all thinking about how to fix the broken culture, rather than thinking about what the author can do, she's done her part in a very brave way by writing this honest article.
Listing what she can/should/coulda/woulda/shoulda is one way to avoid looking in the mirror and all that. It is one reason victim blaming is popular: If it is the victim's fault, then other people don't have to wonder what they might do differently or get off their lazy duff and walk the walk instead of just engaging in smack talk.
I appreciate you making the comment. I don't imagine it will go over well.
> It is one reason victim blaming is popular: If it is their fault, then other people don't have to wonder what they might do differently or get off their lazy duff and walk the walk instead of just engaging in smack talk.
I think the true reason is a bit deeper: victim blaming means that bad events can be compartmentalized to be the victim's problem. So a person engaging in it doesn't have to emotionally deal with the potential problems of the bad event, or even how it could affect them, as they can just say that they would have dealt with it better. A rendition of the just-world hypothesis, really.
That being said, I don't know if I'd call "she should sue" victim-blaming, even though the reason is probably about the same.
That being said, I don't know if I'd call "she should sue" victim-blaming, even though the reason is probably about the same.
This reminds me of some of the BS I have seen where people insist a woman should prosecute her rapist. One of the problems with this line of reasoning is that it makes it the victim's responsibility to try to right this wrong. What if she just wants to put the whole damn thing behind her and not let it eat any more of her life instead of dragging the pain out longer?
It still hangs something on her instead of other people stepping up to bat.
I thought victim blaming referred to specifically blaming the victim for the event itself as / before it happened. Not for what the victim did or didn't do afterwards. Unsolicited advice, in poor taste, but not victim blaming by the definition I'm aware of.
I think most people here asking to sue want to see Uber pay, and they don't really have any equivalent leverage against Uber. There's more victim blaming in the "you should have known how HR works / you should have left" comments.
Sorry if it wasn't perfectly clear: I didn't say that it was victim blaming, just that it is problematic in a way that is not much different from victim blaming. So defending the suggestion as not victim blaming is kind of not great in my book.
It's always worth considering that "she should sue" is actually meant as "she has a clear right to sue, and I would applaud her receiving an appropriate amount of compensation should she do so, because that was completely unacceptable".
I tend to frame the sentiment as "That's lawsuit worthy and if she desires to bring one I wish her good luck and good hunting" for clarity, but I find that often people use "should" conversationally to mean "thing I would love to see happen" rather than "thing I believe the object of the sentence is required to do".
Yeah, I am aware of all that. I appreciate you making an effort to make a clearer distinction -- "that's lawsuit-worthy -- but I am less thrilled with having it explained to me that it is on the victim (or sympathetic women, like myself) to be emotionally sensitive to the intent of random internet strangers sloppily using "should" instead of being backed up on the idea that a predominantly male discussion group really ought to be making more of an effort to frame things carefully when they discuss what some woman has endured at the hands of other men.
> This reminds me of some of the BS I have seen where people insist a woman should prosecute her rapist. One of the problems with this line of reasoning is that it makes it the victim's responsibility to try to right this wrong.
Simply put, that's the system we have. It's designed with the assumption that having adversaries argue according to rules in front of a judge is a good way to figure out what really happened.
It's not necessarily the best way to solve the kind of things it's used for, but we don't have an alternative.
> What if she just wants to put the whole damn thing behind her and not let it eat any more of her life instead of dragging the pain out longer?
> This reminds me of some of the BS I have seen where people insist a woman should prosecute her rapist.
I was under the impression that criminal cases were pressed by the state, not any given individual.
The only thing the state may ask is testimony from the victim. If the victim is unwilling or unable to give that, then the case may just fall apart due to lack of evidence.
That's correct. In a case with a surviving victim, the victim is almost certainly going to take the stand. The 6th amendment to the constitution contains the confrontation clause[1] which says, "…in all criminal prosecutions, the accused shall enjoy the right…to be confronted with the witnesses against him." If someone strikes or stabs or shoots you, and that person stands trial, you will be on the witness stand and you will be cross-examined.
Public support for the confrontation clause isn't popular these days, but I am very glad the courts have continued to uphold it. To quote Crawford v. Washington[2], "Dispensing with confrontation because testimony is obviously reliable is akin to dispensing with jury trial because the defendant is obviously guilty."
> If someone strikes or stabs or shoots you, and that person stands trial, you will be on the witness stand and you will be cross-examined.
Not necessarily. If someone stabs or shoots you in a public place, in full view of 50 other witnesses and 4K recording devices, then your testimony is unnecessary.
That said... in the US most crimes don't go to court so I can't really say what a hypothetical 'open/shut' case will look like in a court trial, because in reality the offender will plea-bargin immediately.
Which puts the pressure on the victim. Very few prosecutors are willing or able to bring a case to trial without the support / testimony of the victim (who is often the only witness).
> Why not talk about how wrong Uber was in every way and at every level - allowing a manager to attempt to proposition new direct reports for sex on their first day, not immediately firing them for this, trying to suppress this when taken to HR, rewarding the perpetrator, killing her career there for vague reasons, let alone all the other dysfunction she mentioned in passing?
Some of these things are actually violations of law in California, and the advice I would give Susan would be to pursue legal action.
I'm confused by your comment. How does it fit with the parent comment? Your comment doesn't seem to make sense as either agreeing with the parent comment (as it nothing about giving advice) nor does it seem to contradict the parent comment (which isn't giving advice or giving Uber some kind of pass). Could you clarify?
We should be talking about the actions of uber and her manager, not what she should or could do. I don't think the author really needs commentary on what comes next, and if she wants it I'm sure she'll know who to ask. We could all usefully reflect on how to stop this happening though.
I hope that helps; if it doesn't perhaps consider why she wrote the article (I doubt it was to solicit comments on what her actions could be).
Personally everyone knows what Uber (and her manager) ought to have done and ought not to have done, and if there were any confusion, the article covered it in depth. I don't know what would be gained by restating it. OTOH, it seems at worst harmless and at best beneficial to offer advice on how to maximize her case against Uber, or to help others who find themselves in similar circumstances (especially those who may not be surrounded by subject-matter experts).
This is correct according to the various employment attorneys who have spoken at various 'managing within the law' training sessions I've attended over the years. Sometimes you can not only sue the company but the individuals who were involved. That should be a disincentive to managers but sadly it doesn't seem to sink in.
Thank you for the context. I have to admit that this thought did cross my mind. I wish Uber would be forced to pay dearly for their treatment of Ms. Fowler, but I don't want Ms. Fowler to be the one that has to sweat to make that happen.
> It is always a bit sad when one of the top characteristic of an engineer from organization X is their political ability to carve out an empire.
When Organization X consistently scoops up the top graduates from the top schools, they end up with a glut of very smart engineers, most of whom are probably overqualified for their day-to-day work. Since brains and talent aren't distinguishing qualities, political cunning becomes the key differentiator.
> I'm a bit surprised she doesn't have at least one law firm trying to get her to be the lead claimant in a class action lawsuit.
Who's to say she doesn't? She just posted the article.
This leads to bad code also bad team dynamics. Ultimately this will reflect on the product and bottom line. For individuals this reads like a culture where the barrel is creating ^bad apples^. Not a good look on a resume.
We have a "whiskey club", and regularly go to the pub where I work.
We don't do it at lunchtime. We don't do it during the working day. 5:30pm on a Friday? Let's have a glass of whiskey together.
Somebody joining/leaving, or we haven't been out together for a while? Let's go to the pub after work one evening.
There is a #drinks channel in Slack where people who fancy a drink after work co-ordinate, and several of will grab each other once a week for a couple of pints.
That does not mean we are drunk when coding. As for team dynamics, it means we know each other better and bond more frequently. Not a problem, I think.
The downside is that for people who don't want to engage in this or can't (have to look after family, etc.), it can feel exclusionary, so we spend some time making sure we do things with those people too.
> As for team dynamics, it means we know each other better and bond more frequently. Not a problem, I think.
Except for the non-drinkers in your team. I suspect that they either
a) feel left out, because a non-drinker at a pub has a boring time, and has to keep justifying their empty glass
b) probably miss out on important decisions if a majority of the important people in a team are present, which is bad dynamics
c) maybe your team doesn't have any non-drinkers. What does that tell you in terms of diversity / inclusiveness?
I'm not pointing fingers at you specifically because you mention explicitly making plans around people who don't/won't drink, but i think there should be more awareness around this, especially since it can seep into the culture quite insidiously, and invisibly.
Some workplaces have sporting clubs that people participate in to grow closer to their coworkers. Yet if you don't like tenis, baseball, basketball, golf, or hiking then you are out of luck.
Every social activity will exclude people who don't like the activity by default. There's no real working around this.
Even if you just have a 'talking' club, you exclude people who aren't natural extroverts or find large group conversations to be maddening.
In essence, there's no way to be perfectly fair... so at best you can have different choices to try to be as inclusive as possible with limited time.
With rare exceptions, I'm a non-drinker. Nowhere in Europe have I ever had an issue ordering a coke instead of an alcoholic drink, even when hanging out with people getting completely shitfaced.
Is this seriously a thing in the US? Feeling like you have to drink if you're surrounded by people drinking? I keep hearing stories like that. Nobody is going to judge you for not consuming alcohol - if anyone does, they're certainly not people I'd want to hang out with regardless of whether drinks are involved.
It doesn't hurt not to give a fuck, once in a while.
I believe I was rejected after a job interview because of not drinking.
Another boss I had any a different job told me he fired someone for not partying with everyone else. If you went to these parties and didn't drink, the boss would harass you all night.
I agree with you that many people are just self conscious, but it's not exclusively that way.
This seems a reason so stupid to reject somebody that either a) they didn't like you but didn't want to tell you the real reason, but didn't care enough to think about a plausibly sounding fake one; or b) you dodged a major bullet as these people had seriously messed up priorities. I'd bet on a) but can't exclude b) completely of course.
The tl;dr is that people who are insecure will attempt to rationalize their feelings, and this frequently includes feelings of judgement and persecution from others where none exists.
Unless being drunk is your idea of fun (in which case it seems doubtful you'd be a non-drinker), I cannot understand how drinking liquid A at a party is any more boring than liquid B.
As a person who does not necessarily enjoy drinking (nor does so very regularly), I would say that being sober around people who are drunk is objectively less enjoyable than being drunk around drunk people.
In fact a graph of my enjoyment as a non-drinker (in my experience) would probably be inverse to a graph of the enjoyment of the people getting progressively more shit-faced.
Drink soda water w/ bitters. Looks like a drink, tastes good, and satisfies anyone actually drinking.
I drink regularly; but every now and then I'll go a week or month without drinking. I'm currently in the middle of one of these periods; but I've still gone out to happy hour or events that involved drinking every day since it's started. I manage to have just as much fun sober drinking soda + bitters.
Peychaud is probably the second biggest brand. Since I drink this at bars, it really depends on what they have on hand. Most good bars will have a selection of 5-10+ different bitters. I like grapefruit bitters; I've also had really good spicy chili bitters. Many like orange bitters. Just ask the bartender for recs, they usually love chatting about this stuff.
The best part of this drink is that they rarely charge me anything for it. I'll usually tip a couple bucks per drink, and everybody ends up happy!
Whatever you choose to do, some subset of the team will end up being left out. Some of my team occasionally go out for a drink+meal. Usually when some remote workers are in town for the day, and we go out after work. Yes, it excludes people with families/other commitments. But lots of other activities would exclude exactly the same people; you can't force the whole team to be sociable after work hours.
We do these things:
1) We don't make any decisions when team members are missing; they have to be done during work hours when everyone is able to participate
2) There's no obligation to drink (why would there be?); several of the team don't drink, and there is no pressure to do so, they get soft drinks/tea/coffee/whatever they like
As someone who is very shy and introverted, it's one of the few times I actually go out socially, and it's a time to unwind and have a chat with your coworkers and associated friends/partners/family. I don't think doing this has any negative impact upon the rest of the team, so long as you don't do any serious discussion and decision making which excludes others.
I can no longer drink, due to medical issues. I'd still go out with my team for the bonding, and probably just leave early every time. I really like how the Chef Community Summit has drinking and dry events, like Game Night. Making inclusivity a goal is fun for everyone!
I once received a bottle of wine as a Christmas bonus from the founders of the small startup I worked at. I was the only person on the the who didn't drink and was pretty offended. Especially since it was well known that I didn't drink since this company celebrated "beer thirty" every Friday.
You were offended by a gift? Just say thanks and give it away or throw it away.
The vast majority of company gifts are useless to many people. Most people can cloth themselves, buy drinks for themselves, buy bags for themselves, etc and have no need for whatever crap the company is getting them as a sign of appreciation.
Unless they demanded you chug the wine in front of them, you really should not have offended yourself this way.
If the gift was specifically chosen for the individual, yeah, I can see being offended. In my experience, once companies reach a certain size, gifts are purchased and given in a one-size-fits-all manner. Inconsiderate, perhaps, but likely not intended to offend.
If you work for a company that has "reached a certain size", you should be aware that you'll have groups of people that make certain one-size-fits-all gifts inappropriate. Like pork products or alcohol in any country with a non-trivial number of Jews and Muslims.
And also coffee of course. And sugary drinks. And chocolate[1] (won't spoil the link but the first phrase mentions "opioids" - like heroin, you know). I'd suggest just give out distilled water. Preferably without any container, so to not contribute to the pollution.
"That does not mean we are drunk when coding. As for team dynamics, it means we know each other better and bond more frequently. Not a problem, I think. The downside is that for people who don't want to engage in this or can't (have to look after family, etc.), it can feel exclusionary, so we spend some time making sure we do things with those people too."
Sounds like a more balanced view of what I've seen at some companies. Implies grown-ups are in charge.
Very much so! Not talking shit-faced, but just normal drinking. It's one of the fastest ways to get to know a person, a lot of people naturally let their guard down, and it provides a casual atmosphere to get to know each other.
It also provides a shared experience that is an easy conversation starter when meeting sober later on "hey, thanks for last night! Where did you end up going after.." etc.
Obviously YMMW, in EU/Denmark it's a very common way to "crash course" people on each other when you suddenly find yourself in a new environment with nobody you know (university, new work). Then again, I'd say EU drinking is a lot more mature than the US one. We usually get introduced to it a lot earlier in life, and have a gentler intro curve rather than going from zero-100 real quick, when entering college or the likes.
Definitely. Alcohol is a social grease. Facilitates having fun, kills off stress temporarily. All conductive to bonding, even if not strictly necessary.
I guess we have different definitions of bonding then, because that just sounds like regular drinking to me. In my opinion a bond is forged through some meaningful connection or meaningful shared experience. I just don't find knocking pints back to be meaningful experience. Its a bond that lasts until the pub closes. I say this as someone who drinks as well.
Alcohol does not create a meaningful bonding experience by itself (unless you're out tasting some very rare and special beverage). It matters what you're doing while drinking. Personally, I find hours-long conversations over beers to be quite good at building rapport with people.
We have a pro-drinking culture at my company due to the nature of the business and I haven't found that it's causing any problems. It's generally done outside of work or for specific events, and I've never felt unsafe on any gathering where a lot of drinking was going on.
This is a red herring, if anything.
I think there's a difference between a culture where people drink a lot vs a culture where people get black out drunk and irresponsible with it, though, and maybe Uber is more like the latter.
>I've never felt unsafe on any gathering where a lot of drinking was going on.
Are you a woman?
I am a good coder with a bad drinking habit who has worked at companies that were ok with drinking on site. While they handled it well and while I love an excuse to get together over beers and discuss coding, it's definitely a smell. Black out drunk has nothing to do with it. Hell, it would be preferable if people just passed out. The problem is all the folks who don't pass out but all of a sudden think this is a good time to declare their love for a coworker's body.
> The problem is all the folks who don't pass out but all of a sudden think this is a good time to declare their love for a coworker's body.
The problem is if they say something like that, the target is clearly uncomfortable, and then nobody else cares. Banning alcohol isn't going to fix something like that.
"We have a pro-drinking culture at my company due to the nature of the business and I haven't found that it's causing any problems."
Anecdotal.
If drinking is done outside work/events this isn't what is being described in the article. What about the personal who a) don't drink or b) harassed by those who do? Drinking at work tells me the place isn't interested in performance or their customers.
Sure, but I'm not entirely sure what else you expect. Isn't your statement also anecdotal?
> If drinking is done outside work/events this isn't what is being described in the article.
Sorry, what article? It's not mentioned in the main OP, and the person a few parents up is talking about what sounds very much like events or after work happy hours. I can absolutely see how that can turn bad, I'm just saying it doesn't have to.
Yup. 100%. Because I'm an adult and I and my coworkers know how to drink responsibly and not make a fool of ourselves and keep things relatively professional.
It's not like I'm taking shots of vodka at the top of every hour - it's maybe having a beer or two at the end of Thursday and Friday, or having a boozy lunch every now and then to celebrate a success or birthday or someone leaving.
>We have a pro-drinking culture at my company due to the nature of the business
Do tell what business this is, because unless the industry is alcohol production, I'm having a hard time believing this is an instrinc quality of an industry and not just a "boys will be boys" excuse.
The following excerpt is the first sentence of the conclusion.
"Attorneys experience problematic drinking that is hazardous, harmful, or otherwise consistent with alcohol use disorders at a higher rate than other professional populations."
This morbid fact is actually taught in law school. Something like 10% of attorneys abuse substances, multiple times over the national average. To demonstrate the scope of the problem: a phone number for an assistance hotline is placed in bold on all Texas state bar cards.
I think you are looking at it too narrowly. Drinking has an important social function in many cultures, western culture among them but by no means alone. Having good social interaction between coworkers is important. Of course, one has to be cognizant of the fact that not everybody drinks and not to exclude people that are not - by making sure drinking is not the only way people can interact socially. But having a round of beers once in a while with coworkers, among other things, is not that bad.
Of course, all that is about social drinking, not getting completely shitfaced to the point one loses control. That is never good.
he said the "nature of the business" made it more pro drinking. but thats not accurate. people's decisions might make for a more pro-drinking atmosphere, but a business can't.
Just because there's drinking at work, doesn't mean they drink while programming.
I've worked at plenty of places with a social drinking culture and never could we be bothered to actually code and drink at the same time. Maybe we might have a boozy friday lunch every now and then, but usually retros and 'meetings' like that followed
Also, I think the statement "extremely heavy on the drinking" is so subjective and up to personal interpretation.
I have to be honest, I know a lot of people who claim that they can write really good code if they've been drinking.
I just absolutely do not understand how that is even possible. If I have ONE beer, it throws off my ability to write good code, or hold all of the concepts in my head.
One of the weekly coworking meetups I go to always ends at a brewery (there is a brewery next door to the hackerspace where it is held), and while it is certainly a lot of fun being there brainstorming things, I don't understand how anybody gets actual code written after drinking.
I've found I'm markedly better at two specific types of programming activities while mildly drunk (the "mildly" part being quite crucial, for me this means two beers or a couple of slowly sipped glasses of whiskey). One is getting a large amount of boring mindless boilerplate out of the way quickly because the alcohol helps me not get too distracted from sheer boredom. The other is re-architecting high level design after getting stuck on a flawed approach - it seems easier to devise and consider more "out there" ideas without getting too bogged down in implementation details prematurely.
Obviously, that's just my personal experience and while I'm quite confident in my sample size, I wouldn't generalize it to anyone else. YMMV.
There are certain types of code which I can unequivocally write better after a few drinks. It's honestly mostly low-complexity drudge work which needs to get done but when sober I can't power through it as fast due to (a) boredom and (b) overanalysis of simple tasks.
This certainly isn't all the code I write (far from it) and it's not for everyone, but it's definitely true for me. That's why I don't think saying alcohol and code can never mix is right, but I agree that it shouldn't be a daily occurrence or the central aspect of company culture. I don't think an optional, after-work happy hour on occasion is such a bad thing though.
There is something called the Ballmer Peak, which has even been demonstrated in one study. Up to a point, the theory goes, creative work benefits from mild intoxication. Beyond that point, productivity goes out the window. For me, I believe that point is around two drinks. For you, it could be teaspoons. Either way, I wouldn't generally drink before the end of the work day.
Personally, I find coding is hardest when you're blocked or stumped. Sometimes it helps to turn off the inner critic and experiment with code in a way that might feel unproductive during normal work hours. How I approach a problem outside of work is my business as long as the solution is solid.
This should go without saying, but everyone's physiology is different. While most people get drowsy from pseudoeffedrine, it makes me hyper. That's why even if one treatment works for most people, it might not work for you.
I'll add that alcohol starts as an upper. It gives you a buzz that makes you feel good and want to do stuff. That's obviously beneficial if you can focus it on a work-related task. Several people here corroborated that hypotheses by saying they do. I've done it, too, in many situations.
Alcohol definitely blunts fast reflexes. If it also hinders coding, it's not for the same reason. If I had to guess, a little could fix anxiety and perfectionism, while a lot will leave you too incoherent to make something work at all.
> If I had to guess, a little could fix anxiety and perfectionism
This is exactly what happens to me, so I sometimes will code after a bottle of beer or a glass of whiskey. But it has to be little - more alcohol and I start losing focus.
For me, it can be a matter of actually doing it. I often suffer from analysis paralysis, so being a little tipsy means that I will actually write the thing. It'll be terrible, but it'll get done, and then sober me can go back and clean it up.
Or I'll go to far, write it, and it'll be unusable.
I used to do this sometimes in university. Haven't done it since entering the workforce, but they say sleep deprivation results in similar performance to being drunk. Not proud of it but I've found myself cornered into nightmare sleep deprived coding marathons by analysis paralysis / procrastination a number of times over the last few years. Alcohol might be preferable.
Back in university days I often wrote assignments while tipsy and then edited them when sober. Cider was just perfect for silencing the inner critic to get some thoughts to paper.
From what I understand, there's a substantial body of research indicating that a slight suppression of the prefrontal cortex can reduce the sorts of inhibitive filters that constrain creative thought. Too much, obviously, and you impair your cognitive ability. Too little, and self-doubt and over-analysis rules.
Anecdotally, I've noticed that I'm significantly more fluent in my third language when I've had a drink or two. I get many, many more compliments. When I'm totally sober, I tend to trip up more and overthink the grammar.
There are lots of ways to reduce a hyperactive prefrontal cortex, including training (practicing art, meditating, etc.), but alcohol is by far the cheapest, quickest, and easiest.
I sometimes code after drinking. Not often, because I'm obviously sharper when completely sober. But when I'm very stressed, my cognitive potential is significantly reduced. Taking the edge off with a single beer results in a great increase of productivity then.
Also, if you think people can't get actual, working code written when shitfaced, then I guess you haven't met the demoscene crowd ;).
This may be the case. I generally say I can't code worth a damn if I've had a beer or two, because my ability to really focus goes way down. But I've also had the experience of getting a bit buzzed and absolutely plowing through a whole bunch of easy-to-write code and enjoying it quite a bit, whereas it was otherwise kind of dull work.
>I just absolutely do not understand how that is even possible. If I have ONE beer, it throws off my ability to write good code, or hold all of the concepts in my head.
There are times when a problem is intractable and I get frustrated through thinking too much about an issue. Alcohol, like caffeine, has its place. I want to stress that I'm not talking about getting hammered at the office, or even mildly drunk, I'm talking about the fact that for some people, a single beer after many hours of work can be helpful in calming them down enough to focus on the whole problem again.
Alcohol can certainly have performance-enhancing effects: comically, the first Olympic disqualification for doping wasn't for steroid use or anything similar - it was for a man drinking "two beers" before his shooting match to calm himself down enough to operate at peak levels.
I can do exploratory coding when drinking, but I won't waste my time or an employers trying to write production code while drinking. As you note, it just doesn't work.
Drinking at work, per se, is not inherently a bad thing. It really depends on culture. It depends on whether it's responsible drinking, social drinking, or it's irresponsible, Bing drinking. There are cultures where people have a beer or two or wine glass during lunch and these people are not typically misbehaved louts. But there is a responsible culture around the drinking.
Why is this getting down voted? Am I missing something in bootload's post? Seems pretty reasonable to me. Don't get me wrong, I like to drink, but drinking and programming don't mix well for me at least. I need my brain cells working, not partying, when I'm trying to write code. Maybe that's my age showing.
Probably because it's conflating drinking and misogyny.
Drinking and programming surely don't mix well. However, a culture that involves, or even promotes, drinking and partying doesn't have to be misogynistic. I've worked in companies that held parties several times per week, with plenty of booze, and they were nothing like what was depicted in TFA.
"Why is this getting down voted? Am I missing something in boatload's post?"
@luckeydude, it's a sort of reaction test for brogrammers who work in toxic environments. I can't think of any job (not after hours) where alcohol improves your performance and output.
"Workcation" is an incredible idea, as is letting employees work remotely for x weeks/ months per year from wherever they want. Even though it's not vacation-vacation it's still a revitalizing, memory forming experience, and if you want a happy motivated work force, I think it's a great idea.
That and a sound proof studio with piano on premise would be enough to make me quit my job.
That said Uber's been on my douchebag radar at least since their execs bragged about threatening journalists. Hopefully your acquaintances already sold their shares on secondary markets because losing ~3 billion a year would worry me if I was expecting to get rich from them.
The booze thing gets exaggerated at many places. It is usually the marketing/HR/business dev/sales teams that indulge in that culture. The engineering team is usually much more constrained in their alcohol consumption, although the media groups them with the frat boys from sales.
I don''t agree with this at all. This certainly hasn't been my experience. Enthusiastic appreciation of craft beer and Scotch are very much a part of tech startup culture.
There are tons of bars at FB. My experience was that people would only go on the fortnightly drinking event, and then it was mostly grabbing an hors dourve and then retiring back to their desk after a single bottle of that. It's pantomime of a drinking culture.
Longtime friend was there in 2011 iirc when they were still "Ubercab" and was cut bc he was "not a culture fit". Aka quiet Russian hacker types not wanted in the frat brotherhood.
>"Crazy, most ex-employees (even the early ones) acknowledge that the culture is bad but they got their $$$ so they won't have to work again for a long time, if ever."
Can you explain why they don't have to work again? How did they become wealthy? Those options aren't worth anything if the company doesn't IPO.
Can you elaborate more on the misogyny that was part of the culture?
So far you've only identified that they like drinking, traveling and were part of the Greek social system in university.
What I'm looking for are instances of demeaning women, discounting their achievements, systemic disapproval for the words of women, favours being handed out on the basis of gender, solicitation of sexual favours in non-equal power relationships, or if no examples can be provided then at least people stating that they are 'in favour' of such, or are lax in enforcing rules against such.
I don't mean this as an attack of any sort (the article gives examples after all). I simply want to know more.
My bad, I have nothing against talking to other witnesses of the crime and wasn't paying attention and didn't know the person you were talking to was an Uber employee and had additional context to provide.
I just thought you were being a jerk and didn't read the article. Oops.
Most recruiters are comically bad at targeting -- apparently there isn't enough downside to just carpet-bombing as many e-mail addresses as they can find -- but this does not mean that recruiting is inherently wrong.
The funny bit was the swapped names, it's like they had a spreadsheet but shifted a column down. Didn't double check the names against emails so I assume it was automated.
Did any of you folks talk about the enormously unethical ways you treat drivers? Those folks who are mostly poorer than you who do the actual work that provides value?
I find it laughable to hear Uber engineers cry about how unfairly Kalanick treats them.
The real problem in Uber's engineering orgs is that Uber hired too many people for too few real projects. From what I learned from my friends in Uber, many teams had largely overlapping responsibilities, and therefore created bogus projects to justify their existence. Their standard MO is picking a missing feature in a service, and then creating a new system that implemented that feature.
It might be okay if all the talents that Uber hired could work together to build truly great software, but hell no, their management created this weird cut-throat culture by enforcing stack ranking with forced curve down to each team of first-line managers. It's hard to imagine that a team with fewer than 10 people had to name an engineer who "didn't meet expectation". Yet that was exactly what happened in Uber. They also doted out disproportional amount of bonus to a few top performers. Naturally, people's expectation was distorted, and chaos ensued.
This is a really interesting observation and something I think doesn't factor into most people's calculus of company culture and execution.
I worked an early employee at a YC startup that was developing a hardware device and I think really ran into similar issues.
There were significant delays with shipping the device which meant that all the teams which had been built up to support its launch had _nothing_ to do for months. People in a "Customer Success" department with no customers. Developer evangelists with nothing to evangelize. Support departments twiddling their thumbs and the worst was the sales and marketing groups which devolved into a Lord of the Flies type environment where they tried latching onto any and every project they could just to justify their existence.
I have literally never seen stack ranking mentioned in any context but horror stories and toxic company culture. What on earth possesses people to keep using it?
Most companies operate on the myth that the people responsible for doing work are interchangeable cogs that can be eliminated and replaced by a new doer with little to no impact to how the company functions.
So if you have enough traumatic brain damage to buy that line, stack ranking makes a ton of sense.
I had this exact same conversation with a manager who seemed suprised when I told him people are not interchangeable cogs. He said that some people may be quicker at a particular technology / domain / whatever, or quicker to ramp up, or do slightly better work, but smart engineers can and do learn anything needed and do work that's good enough after a ramp-up that's short enough. Beyond that, he says, there are minor differences he doesn't worry about as a manager.
This is largely a natural difference in perspective.
The typical interaction between manager & engineer is that a manager tells an employee what to do, and the employee does it. From the manager's perspective, any employee that's reasonably competent will do: success is binary, either you did the assigned task satisfactorily or you didn't.
From the engineer's perspective, if you're good you considered a lot of alternative ways of solving the problem and finally settled on the best. It seems ridiculous that all employees could be interchangeable, because it's a pretty good bet that some engineers did not consider some of the alternative solutions you did. But remember that the whole reason the manager hired you was so that he didn't need to think about the details. All of those alternative solutions are outside of his conscious awareness; he's condensed his mental model of the problem to a binary "is this good enough to ship?", which frees up mental space for him to think about other stuff. Among those engineers that you think of as "not good enough", there are some who may not have thought of the brilliant solution that you came up with but still have code that is "good enough to ship" in the manager's estimation, and those are the irritating folks on your team who IYNSHO always produce shitty code but stay on the team because they have your manager's political favor. And then there are the folks who both you and your manager agree are too shitty to get the job done, and they're fired.
Who's right? Well, both of you, and neither of you. It's fairly likely that you're overestimating the quality requirements for the job, which is why a number of your shitty coworkers still have jobs. It's also fairly likely that your manager does not have complete visibility into all the long-term consequences of all the code being produced, which is why whole teams occasionally just catastrophically fail.
But it's worth remembering that every time you enter a transaction, you're having your work reduced to a pass/fail grade. It's the fundamental bargain you make when you take a job, and it also is the fundamental bargain you make when you sell a product (entrepreneurs are not exempt from this, and it's a major cause of startup failure among technical founders...including, quite possibly, mine). The advantage of producing better work is that it qualifies you for more different opportunities - which may or may not be relevant, depending on whether you take advantage of those opportunities.
> But it's worth remembering that every time you enter a transaction, you're having your work reduced to a pass/fail grade.
This is true as an employee and as a contractor and as a business. The nice thing about transacting as one of the latter two is there is no pretention of the transaction being anything other than a binary one.
I'm still working on the 2nd (or 5th, or 11th, or ~50th, depending on how you count)...not exactly ready to declare it a failure, just, well, a whole lot of pivots.
It's sort of true but a very one-dimensional view on an individuals contributions which is a bit worrying coming from a people manager. I think its funny people go around lionizing individual technical skill and at the same time insist that people are interchangeable.
In my experience most programming jobs don't really require deep domain expertise or share it by osmosis. Ideally a smart, dedicated person that gets a 40 hour a week crash course from experts in the field should get up to speed reasonably quickly.
In the absence of experts there exists a whole slew of technology that democratizes hard fields like game creation and machine learning. You can commit all sorts of sins and still end up with a well functioning product. Partly resting on technology developed as an enabler and partly resting on the sheer amount of available compute.
IMO people are far more easily replaced in terms of making an individual code contribution than they are as members of a team and it's the latter that is significantly more important. Good teams are multipliers for their members. Replacing a team member in a well functioning team is a super risky prospect. Yet we live in a world of frequent re-orgs, teams smooshed together haphazardly and overvaluing individual technical skill.
I don't see that changing anytime soon as it all sort of works and there is an endemic lack of interest.
Outside of truly unique skills, it's basically true - engineers are interchangeable with sufficient time to ramp up.
I learned this lesson pretty early in my career when most senior engineer on the team left. I and everyone else freaked out because he was the only one on the team who fully understood how everything works. But you know who was not freaked out? My manager. And he was right, we did not even miss deadlines. In two month everything was back to normal with other people filling his shoes.
Obviously you can't replace Principal engineer with fresh grad and expect success but most of the work done is not that unique or hard.
>Outside of truly unique skills, it's basically true - engineers are interchangeable with sufficient time to ramp up.
That qualification at the end makes it false.
If I have to give someone 1 year to learn all of the minute details of the behavior of TCP across the various operating systems clients use, the behavior of packet re-ordering in LAG algorithms, convergence times of BGP, etc, then they are most definitely not interchangeable with someone who does know these things.
Any manager who thinks this way is incompetent and will impose massive opportunity costs on the company by not fighting for raises for existing good employees under the guise that they can be easily replaced.
Everything's a matter of degree. So maybe it takes longer or shorter depending on how big the shoes are. But that bundle of knowledge you cited seems learnable in a year.
> I learned this lesson pretty early in my career when most senior engineer on the team left. I and everyone else freaked out because he was the only one on the team who fully understood how everything works. But you know who was not freaked out? My manager. And he was right, we did not even miss deadlines. In two month everything was back to normal with other people filling his shoes.
Have you ever looked around the room and asked yourself "gee, why do we have so many coworkers on this project?" Or said "isn't it nuts that there are some weeks when I can measure my productive output in a handful of hours?"
The current vogue in management is cramming teams into an open floor office and micromanaging scrum points; these measures are introduced because they demoralize and _average_ output, thus introducing slack into the system. That's not a bug -- that's a feature! When someone important leaves the workers can be motivated or "motivated" to increase their output until the proper amount of slack is reintroduced from a hire.
" I don't doubt that has been true on all the teams you've managed. My experience differs significantly, and there's a lot of data which indicates my experiences may have been more representative. Caveat Emptor, of course
Management is interesting because you can be a terrible manager yet still have a successful career at it.
A lot of competent management practices seem counter-intuitive if you've never been exposed to them. Most managers I know have have never even read a book on the subject. Management is often the blind leading the blind. Most likely this kind of environment will scare away any good managers, so the cycle continues.
So, unfortunately, it shouldn't be surprising that these counter-productive practices continue.
That said, reports like this never cease to amaze me.
I realized Uber was in pretty bad shape 2 years ago when the company i was at was trying to hire one of their VPs of Engineering. Not only did they have many VPs of Engineering, they had multiple VPs of Engineering in his specific discipline. It seemed like people were literally only there to get a title and a piece of the kingdom.
Which is funny because my experience at Uber was EXACTLY the same. 3 years ago one of the heads of their department emailed me and asked me to come in and give a talk to their managers as the team wasn't doing so well. After I did this, I asked the VP if they were hiring at my level (I was a director/senior manager at the time) and she said yes. When I came to interview it was clear that I was interviewing for the job of one of the people who were interviewing me. Everyone seemed to love me except for this person, who told me they don't hire managers and that I would have to report to him. He was very junior to me and seemed to only want to keep his title/piece of the kingdom. It was obvious I didn't want to be a part of that, so I declined the offer and not only was the person gone a few weeks later, they were gone from their next job a few months after that. There's some serious political stuff going on at Uber.
It sounds to me like the cutthroat system OP describes would cause the rise of the sort of people who would perpetuate systemic misogyny.
If by "the real problem" they meant "the root cause" then their theory does appear to fit the facts. I personally suspect it was "both" rather than "one caused the other" but have insufficient data to go beyond "suspect".
The jacket drama had nothing to do with gender really and she was making a big deal out of something trivial. I can imagine the scenario is like "ok we're too cheap to create custom jackets for everyone so we will order the jacket size that fits the majority and the minority can try to fit in it". If the gender ratio was the other way around, there would be a similar situation.
The response to other reports are standard. Whether it is a homosexual boss or a female boss, the company will seek to protect itself.
Sure, and we could save money by only have women's restrooms on every other floor, or not at all since we can certainly save money by not hiring women at all. Its just economic sense: we know that its easier to find men, so lets just optimize for men. Then there's all that diversity training. And don't forget women create tension at the office because they are pretty and their women parts distract the men who can't be expected to control themselves.
If you think that any of this is trivial, you are part of the problem.
Your argument isn't relevant for the situation and is very black and white. Wearing male sized team gear is a trivial matter. There are obviously other cases where accounting for every minority is important but this is not one of them.
I do get that it's inconvenient but it's a huge slap in the face to tell a sizeable percentage of your workforce that no, you can't get them a jacket that almost everyone else now has. They could've at least given them something of equivalent value. Even if it might not be sexist, it's a dick move.
I think it's worth pointing out that this kind of male dominated culture doesn't just put off female engineers but male engineers too. As a male I've worked in environments with a high male to female ratio and it makes for a stifling homogeneous type of culture. I've never experienced the kind of sexist culture described at Uber but I imagine that must feel even worse as a male employee. I definitely see few women as a warning sign when interviewing.
'spuz is familiar with male-dominated environments and finds them stifling. 'spuz is unfamiliar with a place as bad as what is described in the article and speculates that he would like that less.
I totally feel the same way too (edit: but almost certainly not worse than how it feels for women). Having worked in both mixed and segregated teams, I much prefer having a good mix. It feels much more natural and normal.
Usually in these cases, these kind of company politics trickle down from the top, so it's unlikely the CEO does not know or has any interest in intervening.
All the companies I worked at that had weird or toxic environments showed that kind of environment throughout most of their structure. A single arsehole in an otherwise great company is usually pushed out sooner than later. If however you notice there are mostly arseholes in your management structure, chances are this goes all the way to the top...
The fact that the story got the traction it did means that the response couldn't have possibly been anything other than what it was (disgust and a promise to look into it). Even if the CEO was directly responsible for this culture the response would be the same. I don't think it's possible to extract anything meaningful from it whatsoever at this point.
He did box himself in a bit with "...will be fired". At least boxed into firing somebody. Not at all saying his outrage is genuine, but initial corporate responses don't usually go that far.
I don't know if that really counts as 'boxed in'. The behaviour Susan described as widespread is absolutely unacceptable and in any sane company would be grounds for instant dismissal. If the CEO is acting in good faith then he wouldn't hesitate to act on any cases found - the fact that they have a new head of HR might indicate that a purge has already begun.
You appear to be reading something into my comment that I didn't mean, or say. The behavior described is absolutely appalling. All I'm saying is that the CEO's initial statement about it goes farther than usual...these are usually carefully crafted to convey sympathy but avoid liability or commitment to action. Usually words like "appropriate action" and not words like "fired".
Once a culture exists, it is very, very difficult to change, even (especially) if you get a new CEO or an acquisition, etc.
It is true that if you are going to _attempt_ to change a culture, it must be motivated from top-down. However, placing that responsibility on the CEO alone is misunderstanding of how culture works.
It's a little akin to saying that culture is the President's responsibility. No, it's everyone's responsibility, and if you want to change it, the influential people in your org (country) must lead and reinforce that change.
The best you can say is that the founder(s) laid the groundwork for the culture. As with anything, changing the foundation later is extremely difficult.
That's what the research says, anyhow. I studied this briefly during my undergrad.
Yes. I've found it proportionally harder to change anything the bigger a group gets.
After a certain size the only way to make a change stick is get rid of people that disagree. Or, you can wait for pressure to wear those people down over... A period of years.
If Ubers culture is really this toxic the only way to fix it would be replacement of a fair amount of leadship in the company.
> It's a little akin to saying that culture is the President's responsibility. No, it's everyone's responsibility, and if you want to change it, the influential people in your org (country) must lead and reinforce that change.
To a point, but when HR gets involved and does not help, that IMHO is often due to the upper leadership being a big part of the problem.
I've seen HR blow off inappropriate behavior when the CEO does or is okay with it.
Anecdotally speaking, I've noticed that Uber has become a dirty word among my friends. For example, someone using Uber will generally just say that they're calling a car rather than naming the service. Lyft doesn't have the same stigma. It should be concerning to management that the company's ethos is repelling customers.
Edit: Management should be far more concerned that Uber is allegedly an environment that systematically enables sexual harassment and discrimination against women.
In the bay area at least a lot of us know at least one or two Uber engineers, and Uber has has an awful reputation around here for a lot longer than the month or so since that strike occurred. As a result of that (plus talking to drivers who work for both services and have strong preferences for Lyft) means that most of my friends were quietly boycotting Uber for years at this point.
I have one friend who worked at Uber and had years of experience working at another tech company beforehand. Uber basically refused to promote her, even going to far as to hire people significantly junior to her into those senior positions. In one case one of the people who was hired blatantly lied on their resume about their past experience, got caught out for it, and was still hired above her.
Even outside of the bay area Uber has taken many reputation hits for their stupid behavior. The whole incident where they were planning on digging up dirt on a reporter to ruin her character shows a huge lack of ethics at the top of the company. The "god mode" application and research into "one night stands" shows they have no respect for privacy.
I also hated the permissions increase they asked for about a month ago. They want to know my location for up to five minutes after I've finished taking a ride with their app? F--- that, uninstalled immediately.
> the perception that they broke the recent anti-Trump taxi strike
Something, it's worth noting, no less true of Lyft. And I think it's a little weird to be demanding owners of infrastructure lock out workers "in support of a strike". That whole reaction was absurd.
I believe they're referring to the fact that Uber took specific action to promote itself by canceling surge pricing at JFK during the strike, not that it did anything passively through inaction.
Lyft did not negate surge pricing that day, AFAIK.
There's an argument that that's economically incoherent - a strike is about restricting supply, and surge is about increasing supply. Turning off surge does not work against the strike.
But that's actually immaterial: surge was turned off a half hour after the strike ended.
That's not the effect of turning off incentives that get more driver to go tot he area. Instead Ubers actions made it so that an increase in demand was not followed up with an increased amount of available drivers at the airport. It doesn't help you if prices are low if there are no cars available.
This was in my opinion a very appropriate way to respect the strike without forcing drivers to not make money unless they chose to do so themselves.
I've had this argument several times already, I'll sum it up one last time:
Lyft operating as normal: "Fuck this strike, making me pay tons of money bc of surge pricing"
Uber operating without surge: "OMG Uber my savior!!!!! / (can't actually find a cab bc of lack of availability) Whatever, not their fault, it's the stupid strike after all"
It was a calculated cynical ploy like literally everything else Uber does. I have no patience with them, particularly in a thread discussing sexual harassment within. Feel free to spin it as "a very appropriate way to respect the strike" or whatever.
Yeah, it seems to me that optimal treatment of a strike would be something like: 1) cap surge (maybe to the typical value for the given time/area), 2) notify drivers when a request is from an affected area, 3) exclude cancellations of those rides from the drivers' metrics.
The biggest concern is that this puts Uber in the position of determining what is and isn't "legitimately a strike".
Among my peer group (Denver) it's been the same. It has alot more to do with what we hear from drivers about the respective companies. For whatever reason drivers are happy to shill for Lyft and are often almost hostile towards Uber. At some point you just get the feeling that Uber isn't what we really wanna be supporting.
I should note: my peer group isn't particularly tech oriented.
This predates #DeleteUber, and it's not only limited to the Bay Area. I've also observed this in Seattle, NYC, DC, Chicago, and to a lesser extent in LA.
The perception is closely tied to what people hear from drivers, constant negative media coverage, and being recognized as the epitome of a douchey tech company. Those three things combine to make using Uber distinctly un-cool in the eyes of many users. (Note that folks will use it anyway, but not talk about it.)
I don't think there is any stigma associated with Uber in Chicago. A lot of people will even say "I'm calling an Uber" even when they're using Lyft (name brand effect).
Definitely true. Case study in "any publicity is good publicity" -- they're always in the news as the assholes, but the market reality is it's a better service than waving your hand and maybe having a cab stop where the first thing the guy says is "meter is broken, cash only".
The services are more or less identical, but I always feel like I'm in the minority when I tell friends I'm calling a lyft.
In the UK, Uber cars are local licenced private hire vehicles with the big "Pre-booked fares only" sticker on the front doors. You have to be licensed to drive for Uber[0].
> My CS classmates - especially women - simply do not apply to Uber,
The sad thing is why do men want to apply there after what is know about it? I wouldn't want to be near any company that treats any of their employees like that.
>The sad thing is why do men want to apply there after what is know about it?
Some students aren't privileged enough to graduate debt-free. Getting into any of these top compensating packages can mean being literally years less time being in debt.
When you are a new grad, you are more willing to put up with stupid nonsense for a year. Puts great experience on the resume and opens more door than previously before which sets up nicely for your 2nd job out of college. This is true for companies like Amazon.
This is true. Also a lot of grads just think, "I'm not a woman/minority therefore it doesn't affect me if I work there". Others think it sucks but will do it anyway because they want to get a big name on the resume and will take anything they can get.
Why do men end-up in dangerous yet good paying jobs? Because testosterone. Most young men are more willing to work a shit job if they can get good money than most women who value quality of life.
If we are going to go that route and using testosterone, I posit having more "testosterone" means standing up for what's right even if it means not getting the highest paying position.
> work a shit job
Right working as a developer at Uber with a high paying 6 figure job is now called a "shit job". I remember when collecting trash and mining was considered a "shit job", I guess we are from different generations...
> I posit having more "testosterone" means standing up for what's right even if it means not getting the highest paying position.
I've lived a long time with very low T. So I don't posit: I experienced how my decision process changed when getting back to normal. I just have to stop some meds and go back down to enjoy less impulsivity and a lot more security based decision making.
> Right working as a developer at Uber with a high paying 6 figure job is now called a "shit job".
Shittier than a simple 9-5 job in some corporation where you can have a good work-life balance, less stress bu less money.
> I remember when collecting trash and mining was considered a "shit job"
They still are. And still have a high percentage of men.
I'm a college senior at a well-regarded engineering school. My CS classmates - especially women - simply do not apply to Uber, in large part because of its reputation for internal misogyny and general assholery. Four classmates interned there last summer, and as far as I know none are interested in returning. A friend of mine was actually warned off by her software engineer father. I've heard stories from friends who've worked there that corroborate Susan's tales of infighting teams and inexplicable reorganizations due to high-level backstabbing. The one woman I know who works there wants out. Susan is a high-profile and credible source; hopefully her post takes Uber's work culture issues from "open secret" to "problem that has public consequences for the company".
The CEO should crack down and take serious steps towards addressing this problem - not just for PR, but because his company is seriously suffering as a result of these issues. Unfortunately for Uber, from what I've heard, Travis is part of the problem as far as Game-of-Thrones internal politics and backstabbing goes. His "move fast and break things" persona sounds like a poor model for subordinates. Between that and the company's relative external success, I wouldn't hold my breath waiting for anything internal to get better any time soon.
Until it does, I simply hope that my acquaintances at Uber find somewhere less shitty to work.