In the world of programming, many are repeated behaviors and good practices, and among programmers There are endless terms and technical words to refer to them, but there are also many others that do not yet have a known name and today I wanted to show you a couple of interesting examples and names.
Post content:
Jargon, terms and funny names within the world of Programming
Ways to Write Code
Yoda Conditions
Write the expected result before the variable.
Pokémon Exceptions
Have ALL your code inside exception handlers.
Catch them all! – The Pokémon slogan and that of these programmers.
Egyptian Keys
The typical case where the brackets are not aligned:
Kame Hame If
Code where you chain too many If-Else because you don't know how to optimize it or want to leave it for later.
Characteristics and type of Code
Unicorn Feature
Something planned in the first stages of the project organization that is then never carried out due to difficulty or time.
Obama Feature
Property that we would all like to add to the application but that will never be approved.
Sausage Code
Because you like how the application works but if you try to read the code it was made with, it may end up disgusting you.
Jenga code
The one where when you try to remove a block of code, everything collapses.
Ghetto Code
Typical block of code that is neither elegant nor good practice, but you need it for the program to work.
Blog-based programming
Code that is copied and pasted to obtain the result you wanted, and that on the blog where you have seen it works but it gives you an unintelligible error.
Hydra Code
When the program does not work and when trying to fix a bug, two new ones appear.
Smudged Code
The one that has been written and deleted so many times that in the end it is implemented with a lot of useless lines of code that you don't even consider deleting.
Bad Breed Code
When you have used so many levels of inheritance that it is impossible to keep track of attributes and functions.
Barnacle Implementation
It is said of that method that is convenient to implement in a certain class, or you do not know where else to implement it, but by doing so you break the principle of sole responsibility.
Types of Bug Reports
Cocky Report
Message sent to report an error where the client tells you how your code should work and gives you suggestions to improve it.
Report with Colocón
They inform you of an error but what is more worrying is how deteriorated the mental health of the person who sent it to you seems.
Vague Report
When they inform you of an error by writing “this thing doesn't work” and they don't tell you or specify anything else.
Fermat's Last Commentary
It is not so unusual for someone to respond in forums or clinics writing that they have found a way to resolve a code error, but many times nothing more is heard from those people.
Waiting
To refer to an error that has been waiting a long time to be solved and there always turns out to be something more important to do.
ReFUCKtorization
Take code that is well written and by wanting to optimize it a little end up with the code not working.
Textually Chained
Too repetitive and inappropriate use of Text Strings, being able to use other classes instead of strings.
heisenbug
An error that behaves differently when you are trying to fix what was happening before.
Higgs Bugson
A hypothetical bug based on a small amount of data appearing in the console and vague, anecdotal reports from users, which is difficult (if not impossible) to reproduce at development time because you don't really know if it's there, and if it's there what it is. is causing.
Hidenbug
An error that destroys data.
Contrabug
An error that appears when you try to solve another error.
White Glove Error
A bug in your code that is good for the application.
Schrödinbug
A piece of code that alternates between failing and behaving as expected.
Bug Foot
An error that you cannot replicate and that has been seen by too small a number of people.
UFO Bug
Report a bug that does not exist but that the client is determined is real and needs a solution.
mandelbug
An error that occurs in such a complex way that the behavior appears non-deterministic.
Paper Bag Bug
An important error that has crept into an application already released to the public and makes its author want to not show his face for a while.
Beginner Magician Mistake
A bug that is created when you receive a message about some error, which is fed back once someone triggers it.
Bug Girlfriend
An error that remains hidden throughout the development process, as if it were telling you that everything is going well, until the application is released to the public and it begins to be seen that it is not right.
Excalibug
An error that all the programmers in a company have tried to fix and none of them have been able to.
Printf Bug
Application that does not work if you delete a line of code that only prints some information to the programmer in the console.
Sources:
All these ideas are taken from the blog Dodge Coder, and translated into Spanish so that you can also enjoy these funny expressions without needing to know English (although you should if you want to dedicate yourself to programming :p).
EN 
ES 