Earlier quoted context omitted.
> There is not much that is more annoying than an author assuming the reader knows the acronyms that they want to use Sometimes you're not the intended audience and that's okay too. Constantly explaining acronyms that everyone in the audience uses daily gets frustrating too. Imagine if every article written for senior software engineers in VC-backed companies had to re-explain what PR, CI, VC and AWS stand for. Or if…
When I write, I typically DO spell these things out. > We accepted a pull request ("PR") for our continuous integration ("CI") server. As a result, CI will now automatically trigger a canary release instead of the old blue-green deployment process, except on AWS where canary releases are not supported. Note that there's no real interruption to the flow of the writing, as I only spell it out the first time it is menti…
Maybe that’s how this author’s bubble feels about FOMO.
I for one don’t think I’ve ever heard the full version of “FOMO” in conversation. Similarly to how everyone I know says “pee-arr” and may not even remember it’s short for something.