The most awesome Stack Overflow question ever posted was later deemed unsuitable for the site, so it was not just closed; it was deleted. It does not exist anymore. The title of the question was: "New programming jargon you coined?" and as you might imagine, it received hundreds of answers. Most of the answers would make you laugh; some would make you laugh hard; some would have you in stitches.
Jeff Atwood saved the top 30 or so of those answers in his blog: Coding Horror - New Programming Jargon, though they are not even the funniest ones. As for the rest of the answers, it seems like they are lost forever.
Or are they?
Well, actually, thanks to archive.org, humanity will continue to have access to this treasure of mirth for all eternity. Here is the link: archive.org - stackoverflow.com - New programming jargon you coined?
Tip: First read the question, then go to the last answer and start reading the answers back-to-front after skipping those with scores of -1, 0, and 1. Make sure you have an hour to spare.
Here is some programming jargon which I have coined:
Magical Incantation
Any statement, argument, command, formulation, or construct that a) is necessary to get something to work as intended, b) one could have never guessed, and c) absolutely no hint for it was provided. Also, any construct that one could never infer what it accomplishes, either after a quick look, or after in-depth study and extensive reasoning.
PEARL
A keyword that I add to source code comments that explain weird, unexpected, usually lame, sometimes incredibly lame behavior of other people's software that my software has to account for and work around.
Blasphemy
Any choice which, although technically valid, nonetheless feels wrong, such as a buffer size which is not a power of two, a raster image when a vector image would have served equally well, a for-loop index variable which is called a instead of i, etc.
Hail-Mary Initialization
The cargo-cult programming practice of pre-initializing a local variable with some meaningless value which is later overwritten with some other value, in all execution paths, before it is ever read. See Hail-Mary Initialization.
Undocumented
adverb: documented in a way that does not really explain anything. For example: // A value of 'null' is undocumented to signify that the file is "not directly accessible", whatever they mean by that. The word is useful for attaching to a comment to succinctly indicate that the comment reflects the official documentation, but the official documentation is nonesense. Often the result of documentation written with the intent of not being wrong rather than the intent of explaining anything. Often used together with PEARL.
Undocumentedly
adverb: attested despite lack of documentation. For example: zork.close(); // undocumentedly also flushes the zork before closing it. The word is useful for attaching to a comment to succinctly indicate that the described behavior was not found in documentation, and was instead divined through guesswork and trial-and-error. Often used together with PEARL.
And here is some jargon which I have picked up and doing my best to increase its popularity:
Get run over by a crocodile
Refers to the possibility that the programmer who has written all of the software that a company depends on might one day quit working for that company or otherwise become incapable of continuing with their duties. Combination of "get run over by a bus" and "get eaten by a crocodile", similar to "rocket surgery".
Search and destroy
Refers to a botched "search and replace" operation that seriously fouls up the source code. Common in scripting languages, where lack of types means that refactoring is practically impossible and has to be faked by means of search-and-replace, and where lack of a compilation step means that the fouled up code cannot be discovered unless an attempt is made to execute that code.
WTFPM
What-The-Fucks-Per-Minute -- a measure of how smoothly (or not) code review is progressing.
Cargo Cult Programming
Doing something in a certain way not because there is any actual benefit in that way, but because some folks proclaim that way to be "common knowledge", or a "pattern", or even "best practice", based on reasons that are either dubious, or severely outdated, or outright fictitious. For an example, see Hail-Mary Initialization.