Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS icon quiz

docs.google.com

Post reply on HN
Print view View original

121–130 of 193 posts

Re: AWS icon quiz

#121

Post by QuinnyPig »

rgallagher27 wrote: post #83
wbercx wrote: post #79

Earlier quoted context omitted.

And why "Amazon" EC2 but "AWS" Lambda? It throws me off every time I look at an alphabetically sorted list of the services. Granted, Microsoft slaps "Azure" in front of some of their services, but Amazon seems to optimise for having "AWS" and "Amazon" mentioned together as many times as possible, as if we need to be reminded.

`Amazon` named services are core building blocks (e.g. ec2 is just servers). `AWS` are services built on top of the `Amazon` services (e.g. Lambda runs on their EC2 machines, Batch runs on EC2 machines). usually

“Some exceptions may apply.”

Re: AWS icon quiz

#122

Post by cheeze »

dkarl wrote: post #39

I work with AWS every day, and I just realized that even though all the symbols have a consistent look, the style is so generic I don't mentally associate it with AWS. To me it looks like symbols from a design diagram where somebody was in a hurry and picked random symbols from their drawing program's image library.

That probably isn't too far off from how they were picked

Re: AWS icon quiz

#124

Post by Waterluvian »

auslander wrote: post #62
Waterluvian wrote: post #22

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…

Console is just for checking stuff. Real infra is managed by APIs.

The console is absolutely indispensable. You need it for your majority of aws users who are doing it for the first or second time. You need it for quick lookups, prototyping, experimentation.

Then when you have the Lego design you want, yes, you whip out cloudformation or bash scripts or Python scripts or ansible or whatever else.

Re: AWS icon quiz

#125

Post by drfritznunkie »

dkoston wrote: post #53

Truth! Names and Icons on AWS were made by people who don’t realize who helpful names and icons can be. If it’s a database, use the cylinder icon that everyone knows is a database and then add some identifier to show which database it is. If it’s DNS, don’t be too clever and name it Route 53. Name it Amazon Cloud DNS. Then anyone knows how to look for it in the console, web search for it, etc. If you want something t…

> If it’s DNS, don’t be too clever and name it Route 53. Name it Amazon Cloud DNS. Then anyone knows how to look for it in the console, web search for it, etc.

Please no. The unique AWS product names while occasionally inconvenient mean that you can at least find relevant information about them when searching, and you know that someone isn't confusing an AWS product with another platform or another style of deployment.

If you really don't like the AWS product names, then Azure is for you. Now go try to search for help with "Azure web apps" or "Azure sql database". Wade through the posts about locally deployed IIS, SQL server and the like.

Re: AWS icon quiz

#126

Post by loblollyboy »

Dwolb wrote: post #2

A note on methodology: typically in experimental surveys you don’t want to prime your subjects with words or phrasing that could lead to positive or negative bias. Additionally, negatively-biased phrasing on a public survey could also attract mostly those with negative views. This would skew your sample even further than solely priming. With that said, I have no idea what any of those icons are.

Dammit dwolb you missed the point!

Re: AWS icon quiz

#127

Post by Slippery_John »

birdtime wrote: post #120
ryanianian wrote: post #111

Earlier quoted context omitted.

It's still priming the responses. If the interest is in drawing a truly 'scientific' result, the hypothesis/wanted-conclusion shouldn't be in the prompt used on participants.

I think the point was that the fault may lie in the poster on HN and not the author of the survey, provided they're separate individuals.

The questions and candidate answers themselves are also heavily biased. The survey is clearly not intended to be an unbiased scientific poll.

Re: AWS icon quiz

#129

Post by QuinnyPig »

auslander wrote: post #62
Waterluvian wrote: post #22

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…

Console is just for checking stuff. Real infra is managed by APIs.

For some. For others it’s indispensable. “You should be smarter” isn’t something I’m prepared to tell newcomers to AWS.

Re: AWS icon quiz

#130

Post by QuinnyPig »

dkoston wrote: post #53

Truth! Names and Icons on AWS were made by people who don’t realize who helpful names and icons can be. If it’s a database, use the cylinder icon that everyone knows is a database and then add some identifier to show which database it is. If it’s DNS, don’t be too clever and name it Route 53. Name it Amazon Cloud DNS. Then anyone knows how to look for it in the console, web search for it, etc. If you want something t…

It definitely has “Potato Quality” moments.
Post reply on HN