Creative guys from Coding Horror once asked Stack OverFlow users an interesting question: “Have you ever coined programming jargon phrases which took off in your team?” The question got over 300 responses with funny coding slang fresh-coined terms which well reflected many programmers’ issues and feelings while coding.
The discussion has been closed by moderators as considered not to the point and “too fun”. But many would agree that the idea of giving funny names to some objects and situations in programmer’s everyday life is both amusing and insightful.
So here are 10 funny names you can call your code, features, and bugs when you need an emotional outlet at work, suggested by the Stack OverFlow community.
- Baklava Code
This is the code which has too many layers. While for sweet Baklava pastry thin layers are just fine, it’s not the case with thin software layers piled one on top of another since these don’t add any value. Balaklava pastry’s phyllo dough layers are supposed to leak and let the honey soak through. I think, you don’t have to be reminded of what leaking layers mean in your code.
- Hydra Code
This is the code that’s almost impossible to fix. Much like the Hydra monster from legends, with every new fix such code introduces more new bugs. Hydra code leaves you no other chance but to rewrite it from scratch.
- Jenga Code
Once you alter one block of such code, the whole thing just collapses. The name derived from the table game called Jenga requiring both mental and physical skill. Players take turns every time removing one block from a 54-block tower construction on the table, making it increasingly unstable until it collapses.
Never ever let your code go in protoduction because this witty term describes the situation when the product’s prototype moves into production!
- A Duck
This is a name for a feature which is added for the only reason - to draw the manager’s attention and be immediately removed, thus avoiding some unnecessary changes in any other aspects of a product.
This adjective is used to describe the feature which is so early in its planning stages it could be imaginary just as well.
Named after its inventor, this term from Wikipedia, describes a bug which instantly disappears or changes its characteristics once it’s attempted to study.
The term’s coined to describe a hypothetical bug whose existence is predicted based on a number of event log entries possibly related to it as well as vague anecdotal user reports, but it is nearly or absolutely impossible to reproduce it on your development machine since you don't know for sure if it's actually there, and what it’s caused by. The name relates to the Higgs boson, an elementary particle considered a fundamental discovery in physics, but is only theorized in 1964 and not proved existing till this day.
- Loch Ness Monster Bug
This stands for anything which is not reproducible or sighted by only one person.
- Mad Girlfriend Bug
Remember the situation when you spot something strange is happening, but the system’s telling everything is fine?