3 ms·
> ...in my days at Amazon Web Services, I saw exactly zero instances of major service releases that, in the opinion of customers, crippled or broke the product.
by alkonaut 5y ago
> ...in my days at Amazon Web Services, I saw exactly zero instances of major service releases that, in the opinion of customers, crippled or broke the product.
The AWS recipe is easy though: add another service instead of touching the old one too much. Great now there are 200 services and approaching them is like learning C++. If one considers "the product" to be the entire offering of cloud services - I'd argue that the PMs fell in exactly the same feature trap.
- lucb1e 5y agoIndeed. The UX is so awful that I avoid AWS for more reasons than simply because it's Amazon's. The next sentence also has me scratching my head: > I’m not going to claim that our UX was generally excellent because it wasn’t; the fact that most users were geeks let us somewhat off the hook. Has this person used the Amazon website? The UI looks much older than AWS. Which I don't mind, don't get me wrong, but it just surprises me for such a popular website, it really looks like the owners stopped updating it in the late 90s (and the search function works like something from the pre-google era as well). Amazon's shopping site is the last one I visit when I'm desperate and can't find it on normal sites, it's always a fun ride of page after page of "this is not what I looked for" and "even if your price field is a string this sort function should work better". No, it's not the geeks that let you not update the UX I think.
- deleted 5y ago[deleted]