3 ms·
I strongly disagree: I'm under no obligation to have followed AWS for the past nine years. Instead, in each field, we should write in ways as self contained,
by graycat 11y ago
I strongly disagree: I'm under
no obligation to have
followed AWS for the past nine
years. Instead, in each field,
we should write in ways as self
contained, and make the minimum
assumptions, possible. In particular,
in technical writing, we should
not have undefined terms.
The research libraries are awash
with single texts that start
with meager prerequisites and
get to some quite advanced
and challenging material.
AWS can do so, also.
I've been in computing for a long
time, but there's no hope
for me to know all the jargon
of all parts of computing.
Mostly jargon is not conceptually
difficult, and the solution to the
challenge of jargon is simple --
just define it.
Parts of computing have long
enjoyed having a closed
priesthood that spoke in
three letter acronym gibberish.
IBM used to do this with
PCP, MFT, MVT, MVS, JCL,
DCB, IMS, DB2, CMS, SQL,
and many more. And there
were some four letter acronyms --
CICS, DASD, REXX.
The concepts
were mostly simple; the gibberish
was a secret language.
Once I gave a grad seminar
on computing and had a lot
of guests from industry.
IBM talked in their gibberish,
but none of the other vendors
did. The students caught on:
IBM wanted to intimidate people
and otherwise invite people
into their priesthood where they,
too, would understand the gibberish.
IBM was the least popular of
the vendors.
- NathanKP 11y agoAWS has documentation at varying levels. If you are looking for documentation that starts at the absolute basics, without acronyms then you are probably wanting the "Getting Started" section of their documentation site: http://aws.amazon.com/documentation/ http://aws.amazon.com/documentation/ The linked article is basically a changelog for devs who have already been using the ecosystem for years, so no its not newbie friendly.
- graycat 11y agoThanks. They would have been doing better for their business if they had made that point clear. Again, my gripe is, better writing is needed. Why? The writing now too often results in absurdly high costs for absurdly poor reasons. The costs to me have me torqued. We're just talking about bad writing.