Since we’re all getting frustated/stressed/excited with our programming, I thought it’d be fun to post some programming jokes to lighten the mood. I’ll start off. This one comes from a friend of mine:
if(time == hammer)
stop();
(If anyone doesn’t get it, don’t be afraid to ask 
)
Wielding only a mouse and keyboard, living off Ramen and Mountain Dew, our brave hero and his team begins the daunting 6-week siege against the mighty C monster.
It got to the point where I walked in on one guy on my team constantly compiling the same thing over and over again. When I asked him why, he told me, “I love seeing the words “BUILD SUCCEEDED”. I’m banking up the number of sucessful builds I have to make up for all the syntax errors I’ll get later.”
How many programmers does it take to change a light bulb?
None. They’ll just say it’s a hardware problem.
True story: There’s a kid in the programming class below us that really looked up to us in terms of style and skill. One day, I decided to search the network drive from another classroom and take a look at this kid’s code to see how he was doing.
I start looking through the source and I see variable names: Ben, Pat, Robert, Tsui…
I almost screamed in horror when I realized he was programming using our names as variables!!!
Talk about creepy. To say the least, we yelled at him for awhile and he no longer makes variable names named after us…
Murphy’s Law.
No matter how many times you scream “I’ve got it now! Last time, it has to work now!!!” after trying to fix a code you’ve written for 3 hours after 2 AM in the morning, you’ll always get a syntax error and an insanly angry mentor waiting for you to finish.
Oh, and the best part is, that after you fustrastedly(spelled right?) work on the code the whole night till dawn, you’re friend comes at 9 AM, takes the keyboard for 2 minutes, mabye does one more fix to what he wrote and the code works.
obviously a true story case. 3 times in a row. Ouch.
Wow, that is kind of creepy o_O. I’m glad no one looks up to me 
, well most people have to look up to me physically since I’ve over 6 feet tall, but enough with the technicalities.
That sounds very familiar. I hate those late programming nights only to find out it was only a hardware error :ahh:
which reminded me of:
C’s motto: who cares what it means? I just compile it!
I had a friend who named a counter that went from 1-10, “midget”. Needless to say the teacher got mad because it isnt a meaningful name and she thought it was inappropriate.
The robot’s too heavy, take out some code.
A few mentors from another team came to our pits today and were asking about how our pickup mechanism works.
Me: “This wheel spins and causes the tube to rotate up. When the tube hits this switch, the program opens up the grabber and raises the elevator to the selected height. Then when the driver gets to the goal, this IR sensor…”
Other team’s mentor: “Hey, did you hear that word he used? Sensor!”
(random guy at ms) Mr. Gates, Mr. Gates, It Compiled!!!
(gates) Ship it!
(whenever our code compiles without a syntax error, thats the first thing I say)
“It Works” = ‘A’ 
Everything on this robot needs to lose weight, I don’t care what you gotta do to get it off just lose the weight, start with the code and work your way back to the hardware.
You may have to be an assembly level programmer to appreciate this. This all has to do with registers.
A programmer’s cheer:
Shift to the left
Shift to the right
push down
pop up
byte byte byte
What do computers eat for a snack?
Computer chips! :] (so its a bad joke… whatever)
Fixing hardware issues in software… like for instance one motor not having any set screws on the elevator… or the gear ratio on the traction motors being to fast to be controlled… priceless! :ahh:
-q
[not really a joke, but you might appreciate this]
I never could figure out why my auton never worked freshman year; I was just learning C and had written this:
if (counter = 5) {
pwm01 = 254;
pwm02 = 254;
counter = counter + 1;
}
Insults:
Go put do loops in your slow loop! (crashes the processor)
Go plug your computer into the tether port! (explodes the system board)
I’m working on some more, so I’ll probably post again, but there’s the ones I’ve got for now.
End Post (VB reference)
if(1==1)
{
actNormal();
}
else
{
temp = black;
black = white;
white = temp;
temp = up;
up = down;
down = temp;
/^^^^^^^^^^^^^^^^^/
//correcting for rip in space time
}
ok heres a good one.
2 programmers are changing a light bulb. programmer #1 takes out the light bulb then programmer #2 puts in the replacement light bulb. As he does this programmer #1 starts to get an angry look on his face . . programmer #2 stops then says " ohh sorry off by one error".
[To a mentor]
In theory, this fix should work great!
[robot entangles arm in rack at full speed]
Oops. 
“We need to save weight. Take out all the white space”
“Just one small change and it will work perfectly.”
“That wasn’t supposed to do that.”
One of our programmers was working for hours on our arm code. He couldn’t figure out why it wasn’t working. I looked over the code, put it in, turned off the safety switch… it worked fine.
Thats why you need more then one programmer. :rolleyes: