The 18F Content Guide
18f.gsa.gov
18f.gsa.gov
My "2c".
Is "WiFi" a buzzword? Is "email" a buzzword? Is "car" a buzzword? Why or why not?
It's like the word "bloat": It's a convenient cudgel to use against anything someone doesn't like which saves them from the labor of having to formulate an actual argument.
Email has a specific meaning too, from its protocol suites. Though they have evolved.
Car is not a buzzword, either.
A buzzword is similar to a thought-terminating cliche. It's a word (or phrase) that is meant to invoke a conditioned feeling with its actual meaning remaining ambiguous, if there is even any. They're usually meant to be positive but empty feelings, hence their ubiquity in marketing. Negative but empty feelings are much more popular in the political sphere, where they're called snarl words.
"The cloud" is a a buzzphrase.
Honestly at this point, for 95% of software outfits, "agile" is a buzzword.
Does that clear it up, or not really? (Honest question)
I will say that "the cloud" can have an actual definition: "We've outsourced that function to a company we communicate with only or primarily over the Internet." It's like outsourcing facilities management.
How often it actually means that I don't know.
I whole-heartedly agree with that suggestion.
> The first response to questions in most online communities I am a part of is "RTFM," how should someone RTFM if there is no M?
FAQs are not manuals, they are workarounds for defects in manuals. They make some sense as a stopgap when the primary documentation may be more time consuming to get corrections published because for bureaucratic reasons, or where lots of people may continue using an outdated version of the primary documentation (in the latter case, the FAQ entries should also reference the proper locations in the updated version of the primary documentation.)
But they should be used as a specific need is identified and removed if it can be completely resolved, not considered a standard thing.