Why is Matt Garmin complaining ??? Slow rollouts were self-inflicted !!
With 27000 layoffs, ridiculous RTO commutes, massive attrition, obviously rollouts will be slower. Vibe coding/Kiro just adds to the problem - having to fix all of the broken that MCP Servers introduces. Why not just hire talented remote devs, comp them well like NVIDIA? Problem solved!
And his release of Q was also a disaster at re:Invent. What's the point of rushing releases ??
Imagine if NVIDIA, Google, and Apple said to their employees: "The first and very most important thing we've got to do is make sure that we deliver on the roadmap that we have. When we're slow and coming out with products, you lose some of that buzz."
Amazon has too many low performers because of a dated hiring process, and the high performers left due to RTO5. So it's not surprising that Garman is mad - he's calling his employees slow, because he already forced the best employees out to save a few pennies. Duh!
Is AWS actually delivering on their roadmap?
"Increasingly, we're finding that when we launch innovative new things at re:Invent it's valuable if we can actually launch them, as opposed to just pre-announce them,"
"Customers want to be able to use our products when we talk about them, and we find that when we're slow and coming out with products, you lose some of that buzz."
"The first and very most important thing we've got to do is make sure that we deliver on the roadmap that we have,"
On one hand, J-ssh0le says "We will need fewer people doing some of the jobs that are being done today, and more people doing other types of jobs. It’s hard to know exactly where this nets out over time, but in the next few years, we expect that this will reduce our total corporate workforce."
But Matt contradicts this by saying that the service teams are already too slow to release stuff for re:Invent. So what is it? Do less with less? Do more with more?