Random
Source Code
Random
When a teammate is taking a first person shooter videogame too seriously and they become unnecessarily mad and impatient with someone on the same team.
From the popular Call Of Duty games where everyone screams at eachother in lobby.
Example 1
"Dude, you suck at this game, I'm so much better than you!"
"You're CODing out right now dude, relax."
Example 2
"You're stealing all my kills, I bet you're cheating!"
"Quit CODing, we're on the same team."
when someone’s heart rate is plummeting and they are going to die without help
When you start writing a code and find yourself overusing conditional/if statements inefficiently, making your code long, messy and unreadable. This strategy is often used by people new to coding, or people that have not planned out how they will write their program. In addition to spamming if statements, if-coders also often do not follow the rules of object oriented programming. They will often only have one class file and will include all of the code for the objects they could have made in that class, resulting in a (very) long code that is hard to read and hard to expand off of, which often leads to code abandonment.
Example 1*
Person 1: Last night I was making a pretty cool game, but I found myself if-coding, and I had to abandon it.
Person 2: Oh wow that's gotta suck.
---------------------------------------------------------------------------------
Example 2*
New Coder: Hey check out this cool game I made!
Experienced Coder: This is a big piece of if-code. Your game sucks.
New Coder: Well my mom thought it was pretty cool...
A guy code that is used to secretly let other men in the general area know that a girl is on her period.
Guy 1: Emergency code red river commenced.
Guy 2: looks like we're going camping this weekend.
Operating with maximum discretion, maintaining secrecy, and avoiding any noticeable behavior. Acting quietly and subtly, akin to "Operation Zero" or a whisper.
"She handled the situation on a coded level, making sure not to make any noise or attract attention."
/brō kōd/
Not to be confused with bro code, the breault code, until now, has been the unwritten set of discourtesies performed by that one guy in your group who cannot be trusted with your girlfriend:
1. Never be loyal to your friends unless it benefits you; YOU are your #1 breault
2. Hoes before bros. Never forget this
3. The best poon is plundered poon
4. If your buddy has a girlfriend you are interested in or have jerked off to a photo of, start casually hitting on her immediately to plant the seed that you want to plant your seed
5. Always keep things cool with your buddy, while making sure to slowly turn up the heat with his girl
6. Whenever you are out with your buddy and his girl, always flex on him by buying as many rounds as possible for him and his girl
7. You don’t fuck with your buddy’s girl, unless he is out of town for at least 24 hours or is asleep, at which time your buddy has waived all rights to his girl and she is considered a forfeiture. If this opportunity presents itself, jettison the friendship with your buddy and make your move; she’s yours now
8. Once you've taken your buddy's girl to Pound Town, don't tell your buddy but feel free to tell his friends. He won't find out
9. If you see your buddy out and he asks any questions, deny everything and ghost
10. Win. High-five, breault
"Watch your girlfriend, man. That dude she is talking to is all about the Breault Code"
Someone who does not see programming as an art, but often creates a dependency hell and writes overly complex spaghetti code for profit and intellectual masturbation.
Many if not most programmers working for Big Tech are coding whores.