You know you've been coding too long when...

Miscellaneous Forums/General Discussion/You know you've been coding too long when...

you start seeing pictures in your code.

Ever seen a cookie, a big huge cookie?

I don't even see the code anymore, all I see is blonde, redhead....

okay first one to guess the quote!

I'm tempted to say it's from NaughtyAlien, but it's from The Matrix.

hihihihih...gurlz rulez.. :)

I write 500 lines of code to make an addition.

... when you're adding support for something that only exists in theory.

Like holograms.

...when the birds start singing outside

When you have to correct yourself for calling the misses an object, she preffers class.

When you reffer to the journey to work as a sub routine.

When you speak more computer languages than human ones.

When you arrive at the computer to type in the program you just wrote.

When you look at the misses and wonder how many polygons she is, and what lighting and shaders would be necessary to recreate her onscreen.


When you speak more computer languages than human ones.


Oh thats miffed it lol, I do loads of computer languages.

..when you want to grab something to eat and your wife calls the police because she thinks you're a burglar.
..when you are interrupted by a guy with a white beard, saying something about a key and a book.
..when you finally managed to get that tile engine running on your vic-20.

..when you singing like she does and claiming that its english, like she does..man..ill be her slave whole day for this show she did...mmmm..tasty....

http://www.youtube.com/watch?v=_RgL2MKfWTo

...when your wife brings you some breakfast.

when you reffer to nocturnal activity as a plugin
when your kettle is a caffine compiler
when you cant go to sleep because somebody on the internet is WRONG

When you go to a fireworks display - like I did last night - and find yourself thinking "Cor, neat particle effects!". Help! :/

... when you're calculating just how much sleep you *would* get *if* you went right now and whether that''ll only make you feel worse.

...when you start talking about technicolor dream dust

when you cant go to sleep because somebody on the internet is WRONG
That one made me laugh.

when you cant go to sleep because somebody on the internet is WRONG
... when you're calculating just how much sleep you *would* get *if* you went right now and whether that''ll only make you feel worse.
Classic :D

calculating just how much sleep you *would* get *if* you went right now and whether that''ll only make you feel worse.

I do this exact thing, "hmm, 2 am, need to get up at 7:45, that's nearly six hours, how much cola do I need to drink if I only give myself 4 hours sleep?"


if post = "You know you've been coding too long when..."
 print("post using code tag")
endif



... when you search for a code solution to your problem and you only get one page of results.

... when for a break, you log onto the Blitz forums...

When you start wondering if you were programmed yourself?

when you cant go to sleep because somebody on the internet is WRONG


http://xkcd.com/386/ :)


What do you want me to do? LEAVE? Then they'll keep being wrong!

when you cant go to sleep because somebody on the internet is WRONG
Haha this one is great. Luckily I've now put that stage behind me.

"You know you've been coding too long when..."

You say..."Not now honey..."
You started at 6:00 and it's now 6:00 again and you think... WTF?
You post a message on the forum asking how to code a loop. ;)
The game now runs at 12fps and yet it still "feels right". :)
Just one.....more......feature...... :)
Your programmer art all of a sudden looks really good..to you. ;)
You're convinced your game is the best thing ever coded.
You just solved your code problem and the "fix" is 1000 lines long.
You coded pong running in 1680x1050 resolution. :) lol..

Ok..that's enough... :) lol...

I remember a long time ago I asked how to make a game 'end' execution...
read here: http://www.blitzmax.com/Community/posts.php?topic=61523#687629 It's terrible...

... when you break everything because you used the wrong variable name somewhere and didn't notice.

When you spend all morning and part of the night debugging your code only to discover that its the very first line in your code thats wrong.

When there's no more room on your computer desk because of all the empty cups, sweet/candy wrappers, crisp/potato chips wrappers and design documents.

When every keyword you type is the wrong one.

When you try and compile a BlitzMax file in MS Visual Studio.

When you try and compile a BlitzMax file in MS Visual Studio.
Rofl!

When you try and compile a BlitzMax file in MS Visual Studio.


Either that, or maybe that's a sign you haven't been programming enough ;-)

... when you start to rock gently in your chair.

You just solved your code problem and the "fix" is 1000 lines long.
Too true. and this...

... when you break everything because you used the wrong variable name somewhere and didn't notice.


..When your motor coordination drops so low that you are unable to type keywords and variable names without several attempts.

..When your motor coordination drops so low that you are unable to type keywords and variable names without several attempts.
I thought that was just me.

When your little brother tugs on your sleeve and tells you he doesn't need to play snake on the calculator anymore.

...and you're at a funeral.

You know you've been programming too long when you can't get to sleep because you're still mentally debugging your program...

... Then you finally fall asleep and DREAM about programming...

... And you realize your dream actually solved the debugging program...

... Then you wake up the next morning and can't remember ONE SINGLE LINE of the debugged code...

... So you punish yourself by coding a virus to destroy all games on your computer...

... Then you remember that debugged code you dreamed up last night...

... Then you realize that you accidentally made your virus TOO smart & advanced, so it also eliminated all the source files for the game you were trying to debug in the first place...

... So you commit suicide by programming your computer to overheat & ultimately explode...

... Then, just before it blows up, you realize you had a backup of your game's source files on a CD in your desk drawer.

If THAT happens, you've definitely been programming too long. @_@

When you wake up suddenly at 3 am and boot up the computer because you just figured how to do 'this or that routine' efficiently, or solved the problem with 'this or that function'...



... when you break everything because you used the wrong variable name somewhere and didn't notice

When said variable misname is a simple, but almost totally undetectable typo like my one recently of 'CurrrentAlpha#'

When you fall asleep, dream about programing something, then wake up and try to start, only to find you wrote it in your sleep. This actually happened to me :D

"When you wake up suddenly at 3 am and boot up the computer because you just figured how to do 'this or that routine' efficiently, or solved the problem with 'this or that function'..."

I do this ALL the time. Strange how that works. I'll have a massive problem, get some sleep...wake up with the solution. Incredibly bizarre but funny too. :)

... Then you finally fall asleep and DREAM about programming...


Kind of how turning off your computer won't even interrupt a game of Tetris if you've been playing it long enough :-?

You when you've been coding to long when:-

Your productivity ends up at 1%, and 100% of that time is on a forum.

Dabz

It's 3:30AM where I am, I've been coding since 7:30PM, my neck is killing me, that's when you knwo you've been coding to long. But the good side is I've got a hell of a lot off my to-do list for my platform game engine.


You when you've been coding to long when:-



You end up in a divorce court! :P

Dabz

@ picklesworth

LOL!


@ picklesworth



2True

Dabz