Counterpoint: FOMO is great marketing strategy for companies
Quite a predatory kind of marketing, but I can believe it makes companies give you more money on the short term.
11–20 of 90 posts
Counterpoint: FOMO is great marketing strategy for companies
Quite a predatory kind of marketing, but I can believe it makes companies give you more money on the short term.
I assume FOMO means ”fear of missing out” in this context, but the article never actually spells it out.
There is not much that is more annoying than an author assuming the reader knows the acronyms that they want to use. This particular case isn't as bad as others, but especially when getting into any sort of technical conversation it's wildly frustrating to see multiple acronyms used with no indication of what they stand for. Then you go to look it up and there's like 29 results that fit the acronym, half of them bein…
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 every article for American audiences re-explained LA, NYC, and EST.
Jargon is useful.
I assume FOMO means ”fear of missing out” in this context, but the article never actually spells it out.
There is not much that is more annoying than an author assuming the reader knows the acronyms that they want to use. This particular case isn't as bad as others, but especially when getting into any sort of technical conversation it's wildly frustrating to see multiple acronyms used with no indication of what they stand for. Then you go to look it up and there's like 29 results that fit the acronym, half of them bein…
So in this case I think spelling out the acronym is neither necessary (as articles typically needn’t define moderately well known words) nor sufficient (as the term’s meaning is more than just the expansion of the acronym).
I assume FOMO means ”fear of missing out” in this context, but the article never actually spells it out.
There is not much that is more annoying than an author assuming the reader knows the acronyms that they want to use. This particular case isn't as bad as others, but especially when getting into any sort of technical conversation it's wildly frustrating to see multiple acronyms used with no indication of what they stand for. Then you go to look it up and there's like 29 results that fit the acronym, half of them bein…
It's used in mainstream television advertisements like the FOMOH ads by the NHL (fear of missing out on hockey).
FOMO is probably as well-known as other acronyms that aren't explained every time they come up: IRS, LGBT, DMV, MLB, NYC, etc.
And, really, if you don't know it, you just do this:
CTRL+T define:FOMO ENTER
I mean, we're already in a web browser...
But here we go, now we're deep in an HN thread about something so incredibly trivial – it really is true that our day jobs are bullshit if we've got this much time to kill on this kind of discussion. (I'm unemployed, what's the rest of y'all's excuse?)
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. This particular case isn't as bad as others, but especially when getting into any sort of technical conversation it's wildly frustrating to see multiple acronyms used with no indication of what they stand for. Then you go to look it up and there's like 29 results that fit the acronym, half of them bein…
> 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…
> 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 mentioned. Nor do I stop to explain what "pull-request" means -- the full name (unlike the acronym) is enough to perform a search on the topic and read about it if needed. And I don't do this universally: everyone I know uses "AWS" instead of "Amazon Web Services" and even pronounces it that way in conversation, so I don't bother explaining that one.
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. This particular case isn't as bad as others, but especially when getting into any sort of technical conversation it's wildly frustrating to see multiple acronyms used with no indication of what they stand for. Then you go to look it up and there's like 29 results that fit the acronym, half of them bein…
This isn't even a technical or business acronym, it's a common colloquial. It's used in mainstream television advertisements like the FOMOH ads by the NHL (fear of missing out on hockey). FOMO is probably as well-known as other acronyms that aren't explained every time they come up: IRS, LGBT, DMV, MLB, NYC, etc. And, really, if you don't know it, you just do this: CTRL+T define:FOMO ENTER I mean, we're already in a…
Earlier quoted context omitted.
This isn't even a technical or business acronym, it's a common colloquial. It's used in mainstream television advertisements like the FOMOH ads by the NHL (fear of missing out on hockey). FOMO is probably as well-known as other acronyms that aren't explained every time they come up: IRS, LGBT, DMV, MLB, NYC, etc. And, really, if you don't know it, you just do this: CTRL+T define:FOMO ENTER I mean, we're already in a…
I said this one isn't much of an issue, didn't I? But it's related to a bigger complaint of mine, which has had non-trivial consequences in the past, so I talked about it.
It's not like the article dives into terms like SE, ICP, AE, CSM, or anything like that.
"Non-trivial consequences," lol, cracks me up. Won't anyone think of all the lost productivity?
Just another hype train that got overheated by a16z and the other smaller VCs that tried boosting the platform and it ran out of steam after it was copied to death and the poor delays and the disastrous release of the Android app.
Now not even the VCs want to use it anymore and have instead moved to YouTube.