3 ms·
I think the issue is more than the tooling randomly spills its spaghetti, rather than some percentage of instances failing, which is obviously expected. Person
by JonnieCache 10y ago
I think the issue is more than the tooling randomly spills its spaghetti, rather than some percentage of instances failing, which is obviously expected.
Personally some of those screenshots would cause me to run a mile if I ever encountered them in my work. Those kind of generic, unspecified errors are terrifying when dealing with other peoples code which is ostensibly stable.
- whateverdudes 10y agoWhich one would make you run a mile?
- JonnieCache 10y agoThe 'undefined' error in the CLI tool, the generic "this operation failed" messages in the dashboard, the unexplained authentication failures. If I encountered those multiple times when trialing a service like this, I would abandon it. It's one thing for there to be errors in OSS code that I can fix, but with a huge and complex service stack like this you're basically at its mercy, and generic errors and failures leave you completely powerless. When something goes wrong with AWS, I've always gotten extensive information which aided in debugging. I guess if you're part of a large enterprise you have a support contract with MS which gives you leverage around issues like this, but that doesn't apply at the level I currently work at.