News for hackers. Stuff that matters.
Re:AWS faulty UX cost our business $7k and they refused to d... by ineedasername on Thursday March 04, 2021 @05:31PM (#26349394)
The definition is overly broad because literally anything the user doesn't like can be blamed on bad UX design. It's too broad to be useful in understanding specific problems. It's like saying anything a person doesn't like in a restaurant was not cooked well.

Also user experience follows pretty heavily from UI design, you cannot separate the two without losing something. But "experience" is also much more subjective: Some might have a bad experience digging through menus while another person might have a good experience, like the way it's all organized. As an example, I found the notification for this issue perfectly acceptable: it let the user know a copy would be made. That is a pretty clear indication that the originals will still exist, and new ones would end up in Glacier. My experience there would be fine.

User experience is unhelpful in this respect because you cannot design your system to satisfy the experience of every user.

Re:AWS faulty UX cost our business $7k and they refused to d... by mikeyla85 on Thursday March 04, 2021 @10:31PM (#26352257)
There's an entire discipline of UX best practices. Some of it is subjective but some of it more generally agreed upon. I don't think you'd find many UX designers who say AWS follows these, and it's up for debate the degree to which it's intentional.
Re:AWS faulty UX cost our business $7k and they refused to d... by ineedasername on Thursday March 04, 2021 @11:47PM (#26352841)
Yep, but none of that means this particular issue was poor UX. Maybe if this particular issue was a very common problem then I would see things differently, but this story also comes from a person who failed to review billing statements from AWS or their bank account transactions for most of a year. It's simply not a situation I can easily blame on AWS.