The good practices I was referring to, were things like: his praise of the documentation culture, the obsession with data security (which I read as a good thing

The good practices I was referring to, were things like: his praise of the documentation culture, the obsession with data security (which I read as a good thing, on behalf of customers). Of course you are right that it was definitely a mixed bag. Your paraphrase isn't wrong either, but I would suggest a modification to it: "it will suck you dry, if either (1) you don't fit in with the company culture, or (2) you are placed in a bad situation on a team with poor leadership and high attrition". Perhaps shockingly, not every team at Amazon is constantly quitting (e.g. my direct team in the last two years has had 1 person voluntarily leave for a better opportunity - and we wished them well, and 0 attrition otherwise), and also some people actually appreciate and gravitate towards some things like, what the author calls "team are fragile" culture (because it is in fact a kind of durability/resiliency that there is less reliance on special rockstars, irreplaceable dependencies, and that teams can be fluid but the product mostly works/lives-on).