Live data from Hacker News

AWS icon quiz

docs.google.com

41–50 of 193 posts

Re: AWS icon quiz

#42
post #15

I don't think they have a 'bad icon' problem as much as a 'too many services' problem. I'm not necessarily saying that they need less functionality, just that they need to divide it up into fewer named/iconed chunks of functionality.

They do have many services, but 95% of their icons, including the early ones, make no sense at all.

Re: AWS icon quiz

#44

Aws feels like it was built by a bunch of siloed teams. There's a lot of design inconsistency I notice every time I'm in the console. For example, deleting entities is never consistent. Some just do it, some ask you to type in the name, some as you to type "delete me". Some entities have a name and a description field that are immutable on creation, even though they also have a unique id. I now have drop downs everyw…

Hah. Guess it depends on what siloed means. With a certain size you need to figure out ways of aligning/comunnicating things - whole AWS is probably thousands of people. You will get siloes.

On top of that: it’s not like all services were build at the same time. Some of them are the “bedrock” of Aws (S3, EC2), some of them are experiments that went viral.

On top of that: Aws is meant to give you building blocks. The magic happens at API/sdk level. The console is there to help you discover and play with the service in a few basic scenarios (and to maybe observer your resources). If you click your way through settings things up you’re going to probably have a bad time.

Re: AWS icon quiz

#46

Aws feels like it was built by a bunch of siloed teams. There's a lot of design inconsistency I notice every time I'm in the console. For example, deleting entities is never consistent. Some just do it, some ask you to type in the name, some as you to type "delete me". Some entities have a name and a description field that are immutable on creation, even though they also have a unique id. I now have drop downs everyw…

AWS was built by a bunch of siloed teams. In the mid 2000's there was a mandate for each separate infrastructure team to open their infrastructure as a service, and they were given tight deadlines. This was meant to solve internal issues but was opened up to the world and AWS was born.

Re: AWS icon quiz

#48
Icons are the least of AWS's UX problems. The AWS console is godawful. It should be a case study in terrible design. I hate every second I spend on it.

Re: AWS icon quiz

#50
Very entertaining and bludgeons you over the head with the point of the survey. I got 6/20 and several correct answers were lucky guesses. I only really recognized EC2, Lambda, and VPC. That doesn't mean the icons actually convey what those are to me though - it's just memory since I use them often.
Post reply on HN