Dear fellow nerds, please write out all acronyms the first time you use them (TFTYUT), our nerd circles may not overlap. After TFTYUT you can use the nice short version however you wish. Many thanks.
I might be alone here, but when I do code reviews I always correct guys when they use acronyms that are not "common knowledge". Things like ASN would be allowed (i can google that easily), but if you're creating something new, that's not a primary domain thing like FancyPowerControl, I don't want to see FPC all over the code.
It may be persnickety, but it just really throws me off when authors create a new acronym, and I have no idea what they're talking about.
Its all about the API for me. I don't want to see Device.FPC, when I have no idea FPC is a thing. I want to see Device.Power
> please write out all acronyms the first time you use them
Like any other writing, it's just about knowing your audience.
I mean, are you really going to write "HN (Hacker News)", "YC (Y Combinator)", "HTTP (Hyper-Text Transfer Protocol)", etc. every single time you use those in a comment here?
Bits of every domain are obscure to someone. But it seems to me that the only domain for which use of acronyms in article titles ever seems to provoke this level of irritation is Microsoft's. Makes me suspect that this particular debate is really just a proxy for a different argument altogether.
Is this really the case? I've been using it since it's inception (never used "Indigo" in production). At the time it was a godsend because our company was moving to a SOA (ahh... the dark ages) using Oracle Fusion Middleware, and judging by the job postings over the years I suspect many other non-Java/Oracle houses also adopted WCF.
I did not realize it was considered an obscure technology.
It may be persnickety, but it just really throws me off when authors create a new acronym, and I have no idea what they're talking about.
Its all about the API for me. I don't want to see Device.FPC, when I have no idea FPC is a thing. I want to see Device.Power