Makes you wonder how these companies ever planned to last during the "next" economic downturn. I don't think anyone bet on a global pandemic causing this shock but the point still stands: These kind of companies were still burning cash at incredible rates 10+ years in. How were they ever going to survive?
Uber cuts 3000 more jobs, closes 45 offices
401–410 of 689 posts
Re: Uber cuts 3000 more jobs, closes 45 offices
#402Earlier quoted context omitted.
Buying a reasonable used compact car probably costs around 2000$ minimum. And a 2000$ car, no matter how nice, has the potential to require much more $$$ in maintenance when things start breaking. Believe it or not, there are people out there who don't have $2000 and these people are also the same ones who can't get anyone to lend them money.
I live in Paris, and I could easily afford a new car (or two) with my income as an SRE. But then I'd have to park it, and just that would double the monthly cost. And then I'd probably use it once a month on average.
Re: Uber cuts 3000 more jobs, closes 45 offices
#403Am I the only one feeling that we should be thankful that these unicorns (whether actually profitable or driven by crazy VC money) have created so many jobs in the past several years?
what did those jobs produce?
Re: Uber cuts 3000 more jobs, closes 45 offices
#404Re: Uber cuts 3000 more jobs, closes 45 offices
#405Earlier quoted context omitted.
That's what business leaders think. Then you get to the critical component where you fire the lead architect/programmer and then it keeps working fine for few weeks, but you find more bugs and you need to upgrade/fix it. Only to find out the documentation if they exist don't help at all and the first 2 tries builds fine so you put it in production only to see everything destroyed. And after 1 year of back and forth y…
An architect that doesn't leave documentation and share knowledge isn't doing their job and management needs to get ahead of this. What if this "key person" decides to find another job?
Re: Uber cuts 3000 more jobs, closes 45 offices
#406Re: Uber cuts 3000 more jobs, closes 45 offices
#407Earlier quoted context omitted.
[flagged]
you are missing the point, it is still a year of work, regardless of gender.
That's all!
Re: Uber cuts 3000 more jobs, closes 45 offices
#408Hard to let go of that many people without losing critical knowledge, Uber will come out of this a diminished company in many ways. Best of luck to those laid off.
Not so sure about that. The company was notorious for having teams constantly rollout competing internal libraries/tools and rewrite them over and over, obviously not having enough bottom-line work to keep everyone busy. A smaller workforce may be able to focus on the work that matters, it doesn't have to imply a lower productivity.
I imagine the same problem is why so many large orgs inevitably turn into hyperstructures of insane management layer cake.. coordination overhead will eventually send everyone begging for the ability to shed work or delegate
Re: Uber cuts 3000 more jobs, closes 45 offices
#409Earlier quoted context omitted.
>> You have man-years worth of work going nowhere as projects get scrapped mid-development. That's better than seeing man-years go into features that get deployed. I witnessed one successful control system company spin up a team of new hotshot UI engineers, all right out of the best schools. After months of work the team "updated" the product. Withing hours the call center was hit with hundreds of "You changed the g-…
[flagged]
Also, "person-year" is vague as "persons" includes non-humans entities such as corporations and partnerships. "Man-year" refers only to work by biological humans. "People-years" might be better but that is plural. Had I been the first I might have used person-years, but when someone else sets a precedent that avoids confusion I'm happy to stick with it despite potential microaggressions.
Re: Uber cuts 3000 more jobs, closes 45 offices
#410Earlier quoted context omitted.
That's more of a failure for the ux and product vision than it is a failure of project management. The trick isn't to just roll out new changes slowly, but to involve the users and figure out what needs to change and how.
>> roll out new changes slowly. That really depends on your customers and the product. In this case, control systems, incremental changes are definitely not the way to go. Imagine if your car made an incremental change to the position of the brake pedal every time you turned it on. In such situations you don't babystep. You announce the change ahead of time, provide your customers with transition training, and make t…