When a programmer writes the conditions for a piece of code in the opposite order for which you would expect to normally read them. (Instead of saying if(variable == constant), the code says if(constant == variable).)
As a programmer, typos are part of your daily workflow. Problems arise though when the typo is proper syntax and neither the IDE nor interpreter alert you to it. Unexpected behavior will happen if it is not fixed.
Mad Girlfriend Bug
When you see something strange happening, but the software is telling you everything is fine.
Talking with other engineers to solve a problem. Practical and widely used, but the term is yet unheard to many.
Adding 2 to a variable, double incremental.
When dealing with logical operators, you run into a phenomenon called short circuiting. This means that the expression will be evaluated only until the truth or falsehood of the entire expression can be unambiguously determined.
A piece of code someone else wrote or you wrote at 4 am that you have no idea how it works, but it does you just have to believe. Aha! I am a magician!
Programmers who write code according to their own rules. They may be very good at writing code, but they don’t generally follow standard processes or policies.
Fixing a problem without fixing it at the source, but rather by adding a workaround elsewhere.
Ever read this? Google’s explanation for server side errors-
“Sorry, something went wrong. A team of highly trained monkeys has been dispatched to deal with this situation.”
The process of taking a well-designed piece of code and, through a series of small, reversible changes, making it completely unmaintainable by anyone except yourself.
An applet, usually Java based, that is not worth anything.
Also known as invisible comments, secret comments, or no comments.