comment on

What kind of acronyms a mortal perl hacker trips across at his immediate/past work place(s)? Are there any that are exceptionally clever? Amusing? Odd? Ugly? Or hard to pronounce?

Although lists of every imaginable acronym on the planet have already been compiled and made available on the Internet (like this one URL: http://www.delorie.com/gnu/docs/vera/vera_11.html), it would be interesting to find out your list of favourite (or not so :) acronyms and the how/when/why you came up with one, or simply the place you found it and why you liked it.

Of course, to begin with, let me share with own list:

YEAH – YEt Another Hack.

In my Perl code, I used to denote any chunk of code that I felt uncomfortable with by simply including a comment like so:
```
# HACK:
#
  … hack code follows…
[download]
```
Not so long ago, I thought of coming up with a replacement for the word ‘HACK’. I had considered switching back to ‘TODO’, but couldn’t then fit it in all cases as with most ‘hack’ code, there wasn’t much ‘to do’ with it other than replace/rewrite it. So, there somehow came the word ‘YEAH’. It was simply a play on the JAPH acronym and quite frankly I was bemused to discover that it does sound like a common utterance ‘yeah!’.
JAPH - Just Another PERL Hacker

Hey, I guess this comes from merlyn?
BUG - Bust yoUr Guts (hey, this may fall under the 'Gore' category, don't you think? ;-)
GUMS - Groups’n’User Management System.

I came up with this acronym while working on a new user management tool at my current job.

_____________________

# Under Construction
[download]

In reply to Odd/Funny/Wacky/Gore Acronyms by vladb

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl: the Markov chain saw
	PerlMonks