Programming jokes

[Adamskiy]

The only cables we screw in are the ones for the radio transmitter and reciever, simply because it's a waste of time and effort for all other cables

[Jake M]

The RS232 Port in our laptop is so loose, we can't screw it in anymore because the screw don't reach.

[JBotAlan]

Robots make you do strange things. I never thought I would ever find myself kicking a robot while saying (directly to the robot, of course) "You are a piece of junk!"

Or saying "That way, you stupid robot!"

Or saying "What the heck are you doing?"

Too many late nights...

The team has just learned to ignore me when I appear incoherent.

[Duncan Macdonald]

Not being a programmer I have received answers to questions in code form.

while(true)
no

[RyanN]

Originally Posted by JBotAlan

Robots make you do strange things. I never thought I would ever find myself kicking a robot while saying (directly to the robot, of course) "You are a piece of junk!"

Or saying "That way, you stupid robot!"

Or saying "What the heck are you doing?"

Too many late nights...

The team has just learned to ignore me when I appear incoherent.

I'll stick to tackling our robot.

[Kingofl337]

I've been known to do this as well.

Originally Posted by JBotAlan

Robots make you do strange things. I never thought I would ever find myself kicking a robot while saying (directly to the robot, of course) "You are a piece of junk!"

Or saying "That way, you stupid robot!"

Or saying "What the heck are you doing?"

Too many late nights...

The team has just learned to ignore me when I appear incoherent.

[LightWaves1636]

Originally Posted by JBotAlan

Robots make you do strange things. I never thought I would ever find myself kicking a robot while saying (directly to the robot, of course) "You are a piece of junk!"

Or saying "That way, you stupid robot!"

Or saying "What the heck are you doing?"

Too many late nights...

The team has just learned to ignore me when I appear incoherent.

LOL, some of the late nights, one of our mechanics would have a conversation with gripper, and then another would talk to a nut on the chassis.

[Alexa Stott]

Originally Posted by bear24rw

lol, that is why we NEVER screw in the cables.. we also had a mentor rip out the teather port on last years RC because it was screwed

That actually happened to us this year. Someone drove the robot and forgot to unplug the tether cable. There were a few loose connections, but we fixed them before ship.

[JohnC]

The year before my rookie year, the "programming team" took turns sitting on the robot with the OI board (joysticks etc) tethered. They found that rallying around the room worked better if they mounted empty water bottles all around the robot for bumpers.

This year, if it was ever past 11:30 pm or so, I would somehow always end up with a ringer around my neck, pacing around the room thinking about my latest coding problem.

[LordTalps]

Originally Posted by JohnC

This year, if it was ever past 11:30 pm or so, I would somehow always end up with a ringer around my neck, pacing around the room thinking about my latest coding problem.

I'm happy I'm not the only one! I've gotten so many looks before that I'm crazy or insane, because I'll do odd things like that. Grab a ringer, rotate it on the floor. Pick up a chair and hold it upside down in the air. Tap any random object that happens to be in my hand at the time.

Of course, the programming team entirely gets yelled at for our brainstorming sessions, which consist of us talking about ideas in a hackysack circle. "Start doing some work!" "We are!" "Your software's not working!" "It's a hardware problem!"

[EricVanWyk]

The first time I taught programming for FIRST, I took a very hands-off/trust-the-student approach. I have tried to maintain that approach over the years, but now I insist that they put the robot up before they put code in.

It was early in the build season, and the new programmers were just getting to learn the system. As practice, I asked them to put a low pass filter on the motor outputs and then experiment with different parameters.

At one point, the parameter put the low passes' knee at .05Hz. At the same time, the variables were accidentally being initialized to all 0 (or was it all 254?). The result was that the robot would turn on, spin, charge.

Without fail, it charged me. It did not matter where I was, it would always find me and hit me. Fortunately, the robot had a few really nice foot/hand holds. I would jump on and hit the main breaker before it hit the wall.

[XxRonnie393xX]

true story: when we were revising last years robot code. we watched cops and wrote down all the code words they use and we used those in our code our mentor was looking over it and hes gets to the equation pot+driving=jail. Never seen and indians face turn read before but i did that day

[blaxbb]

if autonomous = success{
       apocalypse();
}

standard team 1989 coding

[Vashts6583]

I'm reminded of my 2006 autonomous code. In 2005, we had the senior class' valedic. doing our software (If anyone saw Moonraker's autonomous, you can tell how good he was.) Well, 2006 was my first year by myself, so I thought I'd try some basic autonomous. We used it in only one match, and rammed into our alliance partner so hard that the robot fell on its side,. and stayed there the rest of the match. We joked afterwards that "Well, they're better than us in everything else (mainly sports), but they can't survive our robot." Needless to say, i went up and apologized after the match.

Sorry, 1727.

[FunkyRatDemon]

Marketing Team=Self Destruct

I hate you guys...(lucky we didn't finish on time)