You know your in trouble when...
Posted: Thu Aug 03, 2006 7:31 am
You know your in trouble when....
There are more lines of code then there are transistors in your CPU.
When 12 hours is a short time for coding.
When you realize that 42 IS the answer.
If you wake up with code on the screen and you ask "I've never seen such horrible code!".
When you take tips of improvement from your pet cat.
When a girl tells you that she did modeling, you ask which program did she use.
When you wonder if you could optimize your fps counter function in order to gain extra fps
When you move development to your parents' computer
When <Insert high caffeine drink> company sends you a Christmas card
When you spend more time debugging the debug code than actually coding
When all the neat features in the Program only work on your own computer
When your Program Only works with the debugger on
There are more lines of code then there are transistors in your CPU.
When 12 hours is a short time for coding.
When you realize that 42 IS the answer.
If you wake up with code on the screen and you ask "I've never seen such horrible code!".
When you take tips of improvement from your pet cat.
When a girl tells you that she did modeling, you ask which program did she use.
When you wonder if you could optimize your fps counter function in order to gain extra fps
When you move development to your parents' computer
When <Insert high caffeine drink> company sends you a Christmas card
When you spend more time debugging the debug code than actually coding
When all the neat features in the Program only work on your own computer
When your Program Only works with the debugger on