> And for AWS, IAM is a standard abbreviation. That's my point. That point fails: HN has a much larger and more broad audience than AWS. Still, actually, HN

> And for AWS, IAM is a standard abbreviation. That's my point. That point fails: HN has a much larger and more broad audience than AWS. Still, actually, HN should define OP -- I still don't have a good source to know what it means and have been only guessing. That AWS has a smaller audience than HN does not excuse omitting definitions. Again you are assuming that readers of that OP blog are "99%" experienced AWS users, and that's not good. If the blog were only for such users, then I should say so. That I could look around to unwind the acronym, later in the text, elsewhere on the page, on some other pages of the blog, elsewhere at AWS, at Google, doesn't excuse anything. I mentioned some authors with some writing that is astoundingly technical, and there terms are defined as I described. Computing is awash in bad technical writing; I should be torqued at it, and I am; one of the worst problems is poor handling of technical terminology, jargon, and acronyms; the blog post was an example: Either (A) define the acronyms on or before first usage or warn the audience that there are prerequisites. Simple.