Blind Chicken

A term sometimes used in software development, most likely in video games development, to describe the act of submitting files to the project's source control (code or asset) without testing the result locally.

Most likely used in a changelist description to warn others this change is not tested and could be a build break culprit.

Can be used in conjuncture with a Chicken Run or Ninja Chicken to become:
Blind Chicken Run: Not tested, submitted quickly before leaving the office.
Blind Ninja Chicken: Not tested, attempting to fix a prior bug or build break.
Blind Ninja Chicken Run: Not tested, attempting to fix a prior bug or build break quickly before leaving the office.

"Joe had to leave the office, he did a Blind Chicken so that we could start texturing Batman's nipples."

As a Changelist description:
"Batman25 - fixed Batman Rig scene to set proper orientation and fix moonwalking bug - BLIND NINJA CHICKEN RUN"

Chicken Run

A term sometimes used in software development, most likely in the video game industry,

to describe a person's code or asset submit to the project's source control (ie: Perforce)

just before leaving the office for an extended period, ie:(before lunch or the end of day),

without the person staying to see his code / asset submission breaks the build / code compilation.

May also be used in a changelist description by the person submitting the code / asset change to warn others he is conscious about the abomination he/she did.

Also see:
Ninja Chicken
Blind Chicken

Joe did a chicken run again and broke the build.

As a changelist description:
Batman25 - updated main character for tonight's demo deliverable - CHICKEN RUN

4👍 1👎