Maybe I'm totally wrong on this, looking forward to reading other perspectives.
edit: If you’re going to down my post can you at least reply and tell me why? I’m asking questions to learn things outside my own perspective.
1,089 karma · joined September 14, 2012
Maybe I'm totally wrong on this, looking forward to reading other perspectives.
edit: If you’re going to down my post can you at least reply and tell me why? I’m asking questions to learn things outside my own perspective.
My experience is that this behavior doesn't get translated to remote-only workplaces. Casual in-person conversation doesn't shift to chat platforms, it just happens less frequently.
People being remote that miss out on office chit-chat aren't actually missing out on something if their coworkers can help it. I think these interactions are incredibly important for people who value them, and fear of "leaving out" remote workers isn't a very good reason to prevent them.
The most effective workplaces I've been at that have had successful remote workers are the teams that try to consistently involve those people. It's not a set of rules or trainings that makes people do this, it's a mix of cultural values and individual conscientiousness.
This is generally the conversation that's happening here. People talking about competition aren't talking about it as it relates to the quality of the product, they're talking about it from an economic perspective.
> For example, how can it be that a large number of reasonable, intelligent people worry about something they call "cancel culture," while other reasonable, intelligent people deny that it's a problem?
Why “cancel culture” when there’s any number of issues this is equally true for? Why is it only “reasonably intelligent people” oppose it in this example.
This post just seems intellectually lazy. Making sweeping generalizations and then throwing in some appeal to popularity is not a well made point.
I used a macbook with a touchbar for about 6 months. Never again.
>"I am THE ONE. You only need to know me. I am better than all of you."
Wtf, this is the opposite of "up front." You had to poke around and figure it out yourself based on a suspicion. Up front means that they just tell you, no figuring out required.
The other part of this problem that isn't applicable generally to other things, is this is a fairly unique problem to cgroups. By design cgroups don't have a singular implementation or solution, so there are a lot of "competing" solutions. I think some amount of unix philosphy is at play here, to do one thing (or really, fewer) and that's why it seems insane how many systems you have to hook up together to make the thing work the way it should.
I'm fairly devops centric, but I'd still take this with a grain of salt b/c containers aren't my area of expertise.
> Medi-Cal program, the County Medical Services Program, the CalFresh program, the CalWORKs program, or Unemployment Insurance
I'm not entirely sure why, though.
Mattermost didn't work out of the box, and certainly not the way and at the scale Uber needed it to. I'm not overly familiar with the technical details, but one thing in particular stands out as an example. There was a Town Hall channel that every user had to be a member of. This unfortunately did not scale, and not enough ACLs were available to limit all the ways users could use this universal room. Eventually they really fixed the problem, but it was a tremendous pain point for a long time. There were a lot of fundamentally "less than great" things about Mattermost that had to get updated to work for Uber.
There was the amusing time employees found out anybody could change the topic in the room, even if our chat permissions had been disabled. It was absolute chaos for at least an hour, I can't remember if it actually negatively impacted the deployment though it sounds vaguely familiar.
It's pretty telling of employees that badmouth the uChat team. That team ultimately was trying to do what they thought was best for the company, even if at the time it seemed like they bit off more than they could chew. There was no other engineering team so directly visible and exposed to the entire company internally like they were. People dismissive of their efforts are generally not used to the difficulty of making so many very vocal customers happy all at the same time, and could be more sympathetic.
Former Uber engineer here. I can assure you that while our engineering team was massive, there was anything but too little work. If anything most engineers were massively overtaxed. Whether or not the work we were undertaking was meritious and valuable is an entire branch of philosophy I'm pretty sure.
Part of the struggle at big companies is that a lot of existing solutions just don't work. Let me use an example with chat. A few years ago Slack was evaluated as a replacement for HipChat, since Atlassian's outages had finally started affecting us during our own outages.
Everybody wanted to go to Slack, but the cost of Slack was tremendously prohibitive and the state of the service then (as I was told) was such that it could not support a company of Uber's size. Tremendous effort would have been undertaken by Slack to support Uber and they didn't want to expend that effort for a single customer. This was late 2015 early 2016.
There were tons of options, but ultimately an in-house chat software was created. At the time it seemed required to make our own highly reliable chat, considering how distributed engineering teams were. I think if you talk to anybody without the background of how chat evolved at Uber they would think the in-house chat project would have been a boondoggle.
Not all over-scoped engineering projects are actually so noble. There was certainly a ton of "reinventing wheels" going on. There was significantly more "these problems are really hard and I only have bad solutions."
Though if the result is ultimately, "nothing more than interesting repos amongst a sea of interesting repos" sign me up.
You use bold text well before and after these sections, when you're only bolding a few words at most at a time. Once you start bolding whole phrases your paragraphs start looking like striped lines. It was very distracting to try to follow your sentences when my attention is getting drawn to all the bolded text around me. It almost felt wrong at times to read the plain formatted text.
Your content was very engaging and I relate to it quite a bit. The illustrations are fantastic thanks for posting.