Acronym Fatigue Series Introduction: why I'm wary of acronyms
1–10 of 71 posts
Re: Acronym Fatigue Series Introduction: why I'm wary of acronyms
#2LoRa (RF tech) vs LORA (AI optimisation technique) GLM (statistics) vs GLM (AI model)
Re: Acronym Fatigue Series Introduction: why I'm wary of acronyms
#3Re: Acronym Fatigue Series Introduction: why I'm wary of acronyms
#4I enjoyed this article about AFSI.
Re: Acronym Fatigue Series Introduction: why I'm wary of acronyms
#5Re: Acronym Fatigue Series Introduction: why I'm wary of acronyms
#6One thing that irks me quite a bit is when adjacent fields adopt the same acronym for different things LoRa (RF tech) vs LORA (AI optimisation technique) GLM (statistics) vs GLM (AI model)
Maybe we should insist on some standardised expansion of TLAs and XTLAs so you know unambiguously what any particular Three Letter Acronym or eXtended Three Letter Acronym means. I wish I could think of a way of doing that...
Re: Acronym Fatigue Series Introduction: why I'm wary of acronyms
#7Re: Acronym Fatigue Series Introduction: why I'm wary of acronyms
#8Re: Acronym Fatigue Series Introduction: why I'm wary of acronyms
#9I actually think it’s even worse than the author suggests. Acronyms promote the illusion of understanding. You know the words the acronym stands for and it makes you feel a little bit like you know what it means, but you don’t. All names are meaningless words until we assign them a meaning, but acronyms trick you into thinking the name itself tells you something about what it is.
For instance most people don’t know that even though both CAP and ACID contain consistency, they do not refer to the same idea. In CAP it’s about linearizability, while in ACID it’s about preserving invariants.