4 ms·

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

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.

mhurron 11y ago
www.google.com
- simi_ 11y ago
  Just checked it out, looks neat!
jxf 11y ago
> 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?
- strommen 11y ago
  Oh come on. WCF is pretty obscure. .NET is pretty unknown to many HN readers, and even within .NET WCF is not very widely used.
  - deleted 11y ago
    [deleted]
  - bunderbunder 11y ago
    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.
    - deleted 11y ago
      [deleted]
  - ilitirit 11y ago
    > WCF is pretty obscure 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.
  - WDCDev 11y ago
    WCF has quite a bit of adoption in the .NET community. I am currently working on a major WCF project that uses TCP streaming and named pipes. This is the third project I have worked on that uses WCF, and I have been working on the .NET platform since Beta.
  - recursive 11y ago
    I recall getting a pretty negative reaction on Hacker News for not knowing what GHC meant.
swalsh 11y ago
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
- recursive 11y ago
  Hilariously, I've never heard of ASN, and googling turns up a dozen potential meanings.
mrspeaker 11y ago
Except if the acronym is DRY (Don't Repeat Yourself).
- SEJeff 11y ago
  My personal favorite for very poor copy&past code is ARY (Always Repeat Yourself).

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.

mhurron 11y ago

www.google.com

simi_ 11y ago
Just checked it out, looks neat!

jxf 11y ago

> 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?

strommen 11y ago
Oh come on. WCF is pretty obscure. .NET is pretty unknown to many HN readers, and even within .NET WCF is not very widely used.
- deleted 11y ago
  [deleted]
- bunderbunder 11y ago
  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.
  - deleted 11y ago
    [deleted]
- ilitirit 11y ago
  > WCF is pretty obscure 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.
- WDCDev 11y ago
  WCF has quite a bit of adoption in the .NET community. I am currently working on a major WCF project that uses TCP streaming and named pipes. This is the third project I have worked on that uses WCF, and I have been working on the .NET platform since Beta.
- recursive 11y ago
  I recall getting a pretty negative reaction on Hacker News for not knowing what GHC meant.

swalsh 11y ago

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

recursive 11y ago
Hilariously, I've never heard of ASN, and googling turns up a dozen potential meanings.

mrspeaker 11y ago

Except if the acronym is DRY (Don't Repeat Yourself).

SEJeff 11y ago
My personal favorite for very poor copy&past code is ARY (Always Repeat Yourself).