Live data from Hacker News

AWS Tools Suck

cyclic.sh

11–20 of 73 posts

Re: AWS Tools Suck

#12
post #4

Long ago AWS reached the point where feature prioritization was discussed in terms of millions of $$ in revenue. When you have CTOs at Fortune 500 companies waving 10s of millions of dollars in front of your face to build a feature, it's much much easier to prioritize building that over one that is requested by smaller developers with uncertain revenue impact. > The only conclusion is: bad tooling isn't affecting the…

The old problem of data-driven decision making: you tend to only measure success with easily observed metrics. # of features launched is the new # loc.

Re: AWS Tools Suck

#14
Yes they might suck, but that's because of its success and the complexity of the problem - it'll get better over time.

However aws-sdk doesn't need to be 70mb, the console doesn't need to be slow and they don't need over 10 unique services to deploy containers.

We're working on a much improved dev ex for cloud providers and Kubernetes at https://northflank.com - with a fast real-time console, a well documented and useable API with auto generated CLI and API clients. 30 seconds of fun - can I get a production ready CI/CD setup for a repo(s) in 30 seconds? Can I get a HA Redis, Postgres, RabbitMQ provisioned and connected to my code in 30 seconds? These are the questions and solutions that developers will be asking for more and more.

Re: AWS Tools Suck

#15

Yes they might suck, but that's because of its success and the complexity of the problem - it'll get better over time. However aws-sdk doesn't need to be 70mb, the console doesn't need to be slow and they don't need over 10 unique services to deploy containers. We're working on a much improved dev ex for cloud providers and Kubernetes at https://northflank.com - with a fast real-time console, a well documented and us…

I don't find the console slow, but I find it pretty stupid. There are some things that I can't do via the console, only via the API, and some stuff just doesn't make sense. Like why does AWS WAF have its own region selection (that always defaults to us-east-1) separate from the console region selection?

Re: AWS Tools Suck

#17
It only has to be as good as it's competition. Haven't used GCP, but would pick AWS over Azure when it comes to tooling (and a few other categories). AWS documentation tends to be better - for example, Azure fails in giving quick example output for CLI commands. The AWS Console is better than the Azure Portal.

Re: AWS Tools Suck

#18
I got bitten recently by AWS documentation. Several pages strongly imply something to be true, which in practise was 100% false. If I'd wanted to make a living reading text between the lines to work out how they're trying to fuck me, I'd have gone into law.

Re: AWS Tools Suck

#19
post #17

It only has to be as good as it's competition. Haven't used GCP, but would pick AWS over Azure when it comes to tooling (and a few other categories). AWS documentation tends to be better - for example, Azure fails in giving quick example output for CLI commands. The AWS Console is better than the Azure Portal.

I haven't used Azure, but I'd pick GCP over AWS any day. Tools are great, things fit together and feel consistent in a way AWS never did. Feels more like a unified approach to a holistic cloud product, rather than a bunch of teams fighting each other to ship features to gain market share.

Re: AWS Tools Suck

#20
post #18

I got bitten recently by AWS documentation. Several pages strongly imply something to be true, which in practise was 100% false. If I'd wanted to make a living reading text between the lines to work out how they're trying to fuck me, I'd have gone into law.

Please do give feedback if you see anything inaccurate on the documentation. I've submitted feedback many times and they would sometimes reply to my email that they have updated the documentation.
Post reply on HN