> But by the afternoon, nearly 40% of AWS’s DevOps employees were cut in a single internal strike.
> An email memo, which was briefly posted on the internal wiki before being taken down, blamed the cuts on strategic automation initiatives.
It's also very opportunistic, you're telling me you were sitting on this story and you decided to release it right after AWS had issues ?
Exactly. The blog post reeks of bullshit from many angles, not only how AWS does not have "DevOps" roles but also how Amazon and AWS are completely different companies, teams, organizations, everything.
Here's how they sign off their post:
> And do you believe that Amazon cut 40% of its DevOps jobs? Join our (...) Discord server, follow us (...)
It smells of bullshit through and through.
my guess is 4 out of 10, which would make it a single sub team rather than "all devops roles in aws". would love to see something more official.
Good advice.
Layoffs cause loss of institutional knowledge. Minor irritation can balloon into a major outage simply because the person who can fix it easily left the building for the last time.
us-east-1 is the OG region. It has had significant dns problems before. There’s probably a subtle and complicated series of steps for general care and feeding.
Good journalism would identify the process, the owner, cross reference with the layoff list… any of the laid off people would be able to supply those details off the record.
And I object strongly to the mischaracterization of my point as “the smart engineers left.” It’s unfair to the incredibly talented folks that work at AWS to cast the tenured folks as being any more or less skilled—it’s just that they definitively have more experience with the environment.
