151–160 of 193 posts
People suggesting that they follow Adobe's lead. That's all well and good, until you release like 1000 products a year. You tend to run out of two letter combos for your icons.
I mean, is there anywhere in the console where you select/identify a service by its icon alone, without the name next to it? I don't remember any such place. If not... who cares? They're not branded consumer products that need recognition, just a bunch of services and it's not like I'd have any even remotely good ideas for most of these jargony things anyways... :P
5/20
Working without any issues with aws daily.
AWS do put a lot of work into their icons set. That said, we (draw.io) get a lot of direct complains about the icons because: 1) They can't find certain AWS icons (the problem is it's there, they didn't expect it to look like that). 2) They change and move between sets rather a lot. That was more a problem previously, the set hasn't actually changed yet this year. If there's a designer out there willing to create an…
"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"
AWS do put a lot of work into their icons set. That said, we (draw.io) get a lot of direct complains about the icons because: 1) They can't find certain AWS icons (the problem is it's there, they didn't expect it to look like that). 2) They change and move between sets rather a lot. That was more a problem previously, the set hasn't actually changed yet this year. If there's a designer out there willing to create an…
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"
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 deploymen…
I don’t use a search engine though because they have made a good documentation site.
Adding a small identifier (as I suggested, even though jokingly) solves your problem as it’s easy to index:
Azure Cloud SQL Photon
That’s easy to understand it’s a Database and easy to search
Earlier quoted context omitted.
> 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 deploymen…
I have no problem finding documentation for google cloud which has a similar naming scheme. I don’t use a search engine though because they have made a good documentation site. Adding a small identifier (as I suggested, even though jokingly) solves your problem as it’s easy to index: Azure Cloud SQL Photon That’s easy to understand it’s a Database and easy to search
Azure Cloud SQL R364T11
That’s hard to remember but likely narrows the search content drastically
Earlier quoted context omitted.
There isn't just one database app. They have Aurora, DynamoDB, ElastiCache, Neptune, RDS, and Redshift.
Case in point, Aurora is a type of database within RDS. RDS and Aurora are not separate database apps.
That said, they're probably extremely easy to generate procedurally:
http://iquilezles.org/www/articles/distfunctions/distfunctio...
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."