81–90 of 237 posts
The Law of Better is Worse: User-friendly tools prevent skilled middlemen from monetizing their expertise, which stifles adoption of that tool. So on-sellable tools that are too easy-to-use, don't get on-sold. Some examples by contradiction: tax returns, AWS Dashboard, many programming languages.
This is pretty brilliant. Did you just make this up or it a real thing?
I know many people will disagree, but I really miss the VMware fat windows client. (vsphere 5, before they ruined it with the weird flash hybrid that didn't work properly) That, was a paragon of design reliability and speed compared to the AWS console. What annoys me the most is the sheer weight of each page. If you have to context change, its multiple seconds before the page is useable. A classic example is lambda.…
Since their APIs covers everything this should be possible. Be the first UXaaS.
A killer feature: a server by server breakdown of Google Cloud expenses. It is impossible to understand what you are paying for on Google Cloud. They lump everything together in an incredibly confusing bill.
Earlier quoted context omitted.
To an extent that makes sense, but I think Amazon is just generally bad at web design for reasons unknown to me. Their plain old shopping site has been horrible ever since, inconsistent and confusing, and here you can't even excuse this with diving people to an API. Maybe it's to keep people browsing for longer and get them to buy more but that's assuming it outweighs the frustration induced by it.
It’s interesting you mention the shopping site. I have found their site horrible ever since the beginning and only marginally better since done of their belabored efforts to polish some things. I feel like both WAS and the shopping UI/UX are dependent on an overarching common effect; your willingness to suffer in order to get the hit of addiction. On the shopping site it’s the relative speed and gratification of the…
It seems to me that your complaints _are_ what lots of other people actually want to see, (someone saying: yes amazon, please DO show me 20 variations on lightbulbs after i just bought some because Im a shopaholic, i dont do much research and I'm one of the millions of people who click on google ads _all the time_ because i dont know how to go find what i need, the site has to SHOW me what i need)
1) state management/sync is frequently terrible. E.g you are looking at a page with some health indicator and a log view. The last entry in the log is some variation of "transitioned from busted to not busted", but the state indicator doesn't update until you refresh.
2) if you have multiple tabs open at a time (pretty common use case) there is a good chance it will suddenly decide that you have to reload the page for some reason, often when you are in the middle of something
3) live updating. Why the hell do I have to sit there hitting refresh on so many of the views to get up to date data? I've often sat there waiting for something to finish, only to realise it's been done for a while but the page has not updated. This seems closely related to (1).
I find the overall design of the console fine, generally the UI is manageable, but the actual implementation is a steaming pile.
On the Python side, "boto" works well, too.
Earlier quoted context omitted.
If you hate AWS so much, wait until you use Azure. Worst support ever. UI not in sync with the az-cli, documentation super chaotic, lots of basic features from AWS not yet supported in Azure. From my experience, AWS has up-to-date documentation pages for everything. And when something is hard to understand from their docs, you can find really everything you need by searching on Google. Literally, everything. And if y…
My experience is exactly inverse to yours. IMO Azure's documentation, in general, is far superior to AWS's. And my experience with Azure support has been stellar.
Knowledge management is hard.
On the other hand, their CLI tool is very good. I wrote some video training material 3 years ago that goes over setting up an ECS cluster and I decided to use the CLI for just about everything. We interact with a number of resources (S3, load balancers, EC2, ECS, ECR, RDS, Elasticache, etc.) and other than a single flag to login to ECR it all works the same today. I'm happy I chose not to use the web console. The onl…
Their CLI manages to completely lock up my up to date MacBook Pro when simply downloading files and has very strange and conflicting choices of parameters. It is comprehensive, but I wouldn’t call it good
Earlier quoted context omitted.
The only part of the console that I absolutely hate is dealing with the Parameter Store. But I hate everything else about the parameter store too so there is that. CodePipeline is pretty bad too. There is no way you can create a cross account code pipeline from the console.
CloudWatch log filters are pretty bad too. I basically just use ctrl + f now in cw logs to find what I'm looking for.
Earlier quoted context omitted.
I completely agree. I feel stupid everything I try use AWS. I have a pile of credits in my account that I am not using because I cannot bear to try (and fail... Again). It's maddening and they clearly do not care.
What's your level of experience with ops/networking etc.? Because it all boils down to that. If you need a simpler service, maybe you could use digital ocean etc...
Usually when I’m getting into a new area of aws I try to find what they’ve built the technology with. Then I try to go get a good base in that technology, then figure out what AWS has done and understand why/reasoning. This also helps alleviate common concerns about only learning some aws stack. Learn both things, one might one day become less relevant, the other will help you build solid base understandings that last longer.