> The cuts beginning this week may impact a variety of divisions within Amazon, including human resources, known as People Experience and Technology, devices and services and operations, among others, the people said.
They should be completely separate. If they were two independent companies, a low margin distribution and logistics company on one side and a high margin software services company on the other then nobody would suggest merging the two together.
> Which cloud company can casually find 100B cash in a year?
AWS. Because AWS reports close to $11B/quarter, which is over half Amazon's entire revenue, and AWS owns the cloud computing market, on which the whole world runs.
> Amazon includes AWS. They’re not “separate companies.”
Actually, they are. Perhaps what is causing your confusion is that other parts of Amazon, such as Ring or Rivian, are also separate companies, whereas parts such as Alexa and Amazon Music aren't.
By your definition then every little part of “Amazon” is technically a separate “company” including every geo. For the purposes of the discussion at hand they’re all the same. Amazon PXT and finance is the same team as AWS PXT and finance.
> By your definition then every little part of “Amazon” is technically a separate “company” including every geo.
No. My definition is Amazon's actual organization chart as a holding. AWS is an independent first-level branch of direct reports of Andy Jassy, who was AWS's CEO before replacing Bezos. A similar branch is Worldwide Consumer, which groups what you think Amazon actually is, which means the online store, prime, books, devices, etc.
“Little evidence?” If the “aws” partition doesn’t actually exist when IAD breaks, Amazon hasn’t even discovered how to make multi-region cloud infrastructure. That’s a big deal.
The real story from this incident is that Amazon’s “aws” partition doesn’t actually have multiple regions - effectively, it’s all IAD in a trench-coat.
This is a big deal. My employer has already started to look at bringing back our old racks from storage and switching back to on-premises. Cannot imagine he’s alone in that.
Can you elaborate what convinced you of this? We were running mostly in us-west and saw almost no impact, despite using a broad spectrum of AWS infrastructure and tooling.
A manager who’s not doing their job and is never reachable can be pretty demoralizing. That same manager would probably not be great in person either, but at least you’d know where to find them.
As long as a company is able and willing to move out or correct low performers quickly, remote work is fine.