Hacker News Reader

Amazon/AWS teams are so distributed and independent that it the quality of the output of one team very rarely reflects in any way on the quality of the output of another.

This is almost always a good thing.

There are of course centralizations and standardizations - the AWS SDK, Console UX, API guarantees, etc.

But Honeycode has almost no relationship to the rest of AWS, technically, or organizationally.

View on HN

Except what this really means is that nearly any part of AWS you have to deal with has been clobbered together by a series of different teams with little cohesion.

The last time I dealt with AWS and amplify, this was glaringly obvious in several places. Settings pages where one tab looked and behaved radically different from the other. A seeming total lack of communication between teams resulting in badly synced package released with bugs due to version differences. Also frequent omissions in documentation requiring you to hunt it down in github repos or in totally different places(Say Amplify uses X to do something, you might have to find info for using X in an Amplify context in the X docs).

Reply on news.ycombinator.com