> "It's complicated, so it's gotta be good. I must be dumb to not get it."
Having worked with aws a lot recently, this article doesn't surprise me at all actually. When you see the low quality of UI and documentation for most of their tools that users pay for, I wouldn't expect their internal tooling to be any better.
I'm not saying their tech is bad, once things work, it works great - I'm talking about the usability of those tools as I try to use them, and it makes me feel the same as the OP's quote.
If you are using the UI to leverage AWS you arent really leveraging AWS.
AWS is designed to be used via automation and the API.
Disclaimer : I dont work for AWS but have spent many years building relatively large stacks on AWS (thousands of ec2 instances with monthly spend being a couple supercars in value)
yes, but before using the API you need to know which API to use.
If you are looking into using a new service, say, analytics. Which coupling of services do I use, between cloudwatch, firehose, etc etc.
Or reading documentation for example. They have terrible documentation.
Someone using their API/cli is already familiar with aws and how it works. The point, before getting to that point, you need good docs and UI to allow people to discover and learn.
Having worked with aws a lot recently, this article doesn't surprise me at all actually. When you see the low quality of UI and documentation for most of their tools that users pay for, I wouldn't expect their internal tooling to be any better.
I'm not saying their tech is bad, once things work, it works great - I'm talking about the usability of those tools as I try to use them, and it makes me feel the same as the OP's quote.