A term frequently used in software engineering to describe rogue or katty-whompus behavior in source code. Often there is an unspoken agreement between two parties in which only one of the parties has agreed on and has therefore created undocumented, unreliable, and buggy source code.
Bill: Man, I am really tired today.

Jane: Why is that, Bill?

Bill: Well I spent all day chasing software bugs in our local repository and was able to trace it to a geckert.

Jane: Why does that always seem to happen around here?
by codelicious0 February 20, 2014
Get the geckert mug.
A term frequently used in software engineering to describe rogue or katty-whompus behavior in source code. Often there is an unspoken agreement between two parties in which only one of the parties has agreed on and has therefore created undocumented, unreliable, and buggy source code.
Bill: Man, I am really tired today.

Jane: Why is that, Bill?

Bill: Well I spent all day chasing software bugs in our local repository and was able to trace it to a geckert.

Jane: Why does that always seem to happen around here?
by codelicious0 February 20, 2014
Get the geckert mug.