3 ms·
> Poorly designed, failure-prone, brittle internal tooling was a time and energy sink to the point where even the most trivial deployment change was a nail-bite
by rad_gruchalski 4y ago
> Poorly designed, failure-prone, brittle internal tooling was a time and energy sink to the point where even the most trivial deployment change was a nail-biter.
Considering rather good quality APIs they expose to the external world, this is shocking to read.
- sbarre 4y agoInternal tools never get the same attention as public-facing products. Public facing products have competition. Internal tools have a captive audience that must use them, no matter what.
- krageon 4y agoGood is a big word, but they exist and have docs. A lot of the time the docs are even correct, if you can find them.
- rad_gruchalski 4y agoI have most often interacted with their APIs via the golang library. Compared to Azure, the AWS stuff is pretty solid.
- krageon 4y agoEveryone says this, but in terms of discoverability of the actual apis I have found the opposite is true. Azure tends to have docs with small mistakes, but they are extremely thorough. With AWS it seems to be a tossup: You can be lucky and have complete and accurate information, or you can be fucked.