Couldn't agree more — God the overuse of acronyms is so frustrating. I try to always write it out at least once before using it, even casually in slack every new context.
Something like:
Our Objective Key Results (OKR's) are looking good this month, however when looking at our OKR's let's be sure we update them consistently. That way Management has good visibility of OKR progress and blockers.
Cron isn't actually an acroynm, it gets its name originally from the Greek personification of time Chronus. This makes sense, as cron is a tool for running tasks at chronological intervals.
You can include these also :
POC : Proof of Concept
RFQ : Request for Quotation
RFI : Request for Information
PO : Purchase Order
WO : Work Order
SKU : Stock Keeping Unit
Also a really important one is TMA: Too Many Acronyms.
Pro-tip: always try to avoid using acronyms. When you do, define it on first usage.
Couldn't agree more — God the overuse of acronyms is so frustrating. I try to always write it out at least once before using it, even casually in slack every new context.
Something like:
My favourite is TITSUP, Total Inability To Support Usual Performance
It is great to have such a list in a commonplace. You can also consider adding the below item in your list,
JSON - JavaScript Object Notation
Typo mistakes to be fixed,
WSYWG -> WYSIWYG
CPP -> CPC: Cost per Click
CRT -> CTR - Click Through Ratio
Fixed ✔️
Thanks!
Cron isn't actually an acroynm, it gets its name originally from the Greek personification of time Chronus. This makes sense, as cron is a tool for running tasks at chronological intervals.
you put CRO two times but awesome bro.
really helpful..
Fixed — thanks ✔
Added — thanks ✌️
You can also add:
KT - Knowledge Transfer
ETA - Estimated Time of Arrival
You can include these also :
POC : Proof of Concept
RFQ : Request for Quotation
RFI : Request for Information
PO : Purchase Order
WO : Work Order
SKU : Stock Keeping Unit
Added — thanks!
Am I the only one bothered by the column inconsistency?