Code-971 / Code-972

Code used to tell a friend that you are going to take a piss (971) or a shit (972). Sections also exist to define the length of time of the said procedure.

Friend 1: yo man why you got that look on your face...
You: Man i gotta take a Code-972 major
Girlfriend: You boys and your lingo.
Friend 1: haha she doesnt know what the hell we are talking about.
You: Yea man actually its gonna have to be a section 25
Friend 1: DAMN!...BOI
Code-971 / Code-972, the choice is up to you

by Behzad July 15, 2006

code senescence

The process by which unmaintained computer code degrades to a non-working state over time.

I have a presentation in 5 minutes, and my 3 month old code has undergone code senescence

by D G July 25, 2007

The Playa Code

see playa phi playa.

"I go by The Playa Code, baby".

by Used by permission of PlayaPhiPlaya June 9, 2007

Preppy Code

Heavy use of proprietary code and technologies in a project/solution

Joe is such a preppy coder, he can't write anything without using the newest whatever from company x.

I really don't know why they've use technology x from company x it would have been much simpler to write one or two functions of their own.

by Dispel February 15, 2013

sARGHrce code!

source code: human-readable instructions in a programming language, to be transformed into machine instructions by a compiler, assembler or other translator, or to be carried out directly by an interpreter.

argh: what a pirate says to express annoyance, dismay, embarrassment or frustration.

sARGHrce code!: what a pirate says to express annoyance, dismay, embarrassment or frustration source code.

"sARGHrce code!" - says a pirate

by [e-mail] February 25, 2013

The Code of the Biti

1. Taking things a biti at a time so one does not get overwhelmed.
2. Taking 1 literal step forward.

Things were stirring heavy in the pot so I decided by the code of the biti.

by dannydadino April 26, 2014

if-coding

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...

by YetAnother13YearOldBoy November 12, 2013