Acronym assumptions.

[Trizor]

Monks, have you ever used an acronym with the assumption that everyone you're speaking to knows it. Fair warning, at least one of them probably doesn't and will try to decode it without interrupting to ask.

Earlier today I was discussing configuration options with a friend of mine, I said I planned on using Config::Tiny and just some simple ini files, but I was having trouble validating the creation of a nested structure using some user-defined sections for the nesting, so my friend suggests YAML thusly: "Why don't you use YAML?".

Now I had heard YAML before, but always as an acronym, and had guessed that it stood for Yet Another Markup Language and decided that quipping back: "You really expect me to learn Yet Another way to configure my programs?". This fetched merely a blank stare from someone who usually laughs at even worse puns.

The misunderstanding was quickly clarified, and in this case harmless, but the next time you step to use an acronym, think, "Does everyone really know what I'm saying?"

Note: For those who don't know, YAML stands for YAML Ain't Markup Language

[McDarren]

Because I've been involved in Tech Support at various levels for a number of years, I tend to use PEBKAC quite a lot, and I find that very few people know what it means. But that's probably a good thing, as I imagine there are a fair number of users that could take offense at being told "Ah, yes. I know your problem. Seen this many times before - a classic case of pebkacery" - if they actually knew what it meant ;)

I've also seen a few here at PM that I'd not previously seen elsewhere. YMMV is one example - and in fact, your post prompted me to look that one up right now ;)

Cheers,
Darren

[Fletch]

Once they start wising up to PEBKAC you can switch to calling them 'ID10T' (pronounced "eye dee ten tee" out loud, of course) problems.

[liverpole]

Heh heh ...

It reminds me of the time, at the first computer company I worked for, when we were expecting a visit from some people at DEC (Digital Equipment Corporation), which acronym I thought was pretty universal.

Checking with the young secretary, I asked "Are the people from DEC here yet?", to which she replied "No, but there are some people from Digital waiting in the lobby".

So I have to agree -- one person's ATESK* is another person's puzzled stare.

(*) ATESK = "Acronym that everyone should know"

[apl]

In another thread (on inadvertantly violating a Software patent), one responder prefaced his comments with the standard IANAL disclaimer.

I realized this meant I Am Not A Lawyer, but was struck by the notion that I (am) anal would describe a lawyer...

[Fletch]

IMSMC, IANAL is a very common TLA that I was first exposed to aeons ago via USENET. When in doubt, there's always TJF. And it's not like you can't STFW for them really easily (remember, GIFY).

Ahem. I'll stop before people start going "OMGWTFBBQ".

At any rate: HTH. HAND. :)

[bibliophile]

Heh - that brought to mind a recent Ctrl-Alt-Del comic:
http://www.cad-comic.com/comic.php?d=20070407

:-)

[Ojosh!ro]

Bâââh! acronyms


I prefer not to use them. It's bad grammar, it's unclear and it's lazy.
Besides that, most acronym-users seem to think that they have the only possible explanation for an acronym. Try to explain to the union of pot-smokers that you want the uninterruptable powersupply sent via universal parcel service.
The 'YAML' kind of acronym you refer to is the worst... even if you unpack it it's still not clear what it actually means. Those always give me a symlink-to-parentdir feeling. ;)