Live data from Hacker News

AWS icon quiz

docs.google.com

161–170 of 193 posts

Re: AWS icon quiz

#161

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…

To state the obvious, you really should not be using that console to do anything. Basically browsing the console is already technical debt.

Re: AWS icon quiz

#162
I use AWS every day and got 17/20. Thanks to a couple of lucky guesses.

But, I believe that at least two of the questions have incorrect/incomplete answers:

One of the questions that requires a typed answer (instead of multiple choice) shows an icon that is used for both EC2 & Appstream. However, only EC2 is considered correct.

In the Route53 icon question - there are multiple versions of the Route53 icon used in different places (do a google image search and you'll see a dozen variant). The icon in the top left ("Pole with two offset rectangles") is used in the console - but this is considered an incorrect answer. The icon in the top right ("Pole with two slightly less offset rectangles") is sometimes used elsewhere and is the only answer considered correct.

Re: AWS icon quiz

#163

Earlier quoted context omitted.

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

Not every service has an API, especially new ones. They tend to launch things console first. Look at Alexa. It took over a year to get API, and it still doesn't have CloudFormation support.

I don’t think Alexa is considered an AWS product/service. While you need AWS’ Lambda to make it work, Alexa is an Amazon (versus AWS) product.

Re: AWS icon quiz

#164

Earlier quoted context omitted.

This is a bullshit answer. Your design language is the worst and cannot be defended. Amazon has literally all the money. Hire a team, give them the mandate and listen to their suggestions/solutions. Asking for spec work is some serious bullshit. "Don't like it, make your own... if we like it we might start using it! Then you can say you built the AWS icons for free, I'm sure that will be great for your career"

I think the guy you're replying to is from draw.io a systems diagramming platform and not from Amazon.

... does not change the odor of his answer.

Re: AWS icon quiz

#165

Earlier quoted context omitted.

I think the guy you're replying to is from draw.io a systems diagramming platform and not from Amazon.

... does not change the odor of his answer.

draw.io is an open source project [1], you're suggesting we hire a team to implement the AWS icons?

Asking for others to contribute to open source is a generally accepted concept.

https://github.com/jgraph/drawio

Re: AWS icon quiz

#166
post #95

Earlier quoted context omitted.

There isn't just one database app. They have Aurora, DynamoDB, ElastiCache, Neptune, RDS, and Redshift.

"fast sql database," "fast nosql database," "redis cache nosql database," "graph database," "rds (is actually named right lol)," "big analytics SQL database."

Amazon Relational Database Amazon Keystore Amazon Warehouse Database Amazon Analytics Database

I agree these would be much more descriptive.

Re: AWS icon quiz

#167

Earlier quoted context omitted.

Not every service has an API, especially new ones. They tend to launch things console first. Look at Alexa. It took over a year to get API, and it still doesn't have CloudFormation support.

I don’t think Alexa is considered an AWS product/service. While you need AWS’ Lambda to make it work, Alexa is an Amazon (versus AWS) product.

Ok, fair point, but you can see the same pattern with other services. Look at any of the AI services for example. Everything was console first.

Re: AWS icon quiz

#168
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

I don't believe that's the reasoning; and although I worked at AWS in the past I don't know for sure what's the reasoning behind choosing "Amazon" or "AWS" prefix for a service name.

For example, RDS is definitely a service built on top of other core services (EC2, S3, KMS, Route 53), its name is "Amazon RDS" and not "AWS RDS".

Re: AWS icon quiz

#169

Earlier quoted context omitted.

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.

I've been to two AWS Summits (Stockholm) and most if not all AWS employees explicitly point out that you should never use the console for anything serious. It might be good for presentations, but it's horrible when you need to manage infrastructure.

Re: AWS icon quiz

#170

Speaking of AWS, shouldn't they also hold a poll on naming? I've seen some saner alternatives in the wild: https://www.expeditedssl.com/aws-in-plain-english .

A lot of those names are actually pretty sensible, but who thought "Amazon Unlimited FTP Server" was a good alternative to S3?
Post reply on HN