"Quotes" that were said during build season

[$~-M.E.C-~$]

Everytime at the end of meetings the president or one of the metors will say, " you don't have to go home, but ya can't stay here!"

[The Zevling]

"Stupid Lollipop"
- said while trying to find a place for our camera where it won't be blocked by our claw mechanism*, which is a large circle on a stick. Hence "lollipop". The group working on the lollipop is, of course, refered to (at least by me, anyway) as the lollipop guild.

"Excuse me, I want to stick my head in the robot"
- me trying to get a cameras-eye view from a potiential camera spot.

*our claw mechanism grabs outward, so before it was the lollipop, it was called the Walc. It is actually in the code as the Walc, so it's official.

[Radical Pi]

"Look, if the Mythbusters have taught us anything, it's that an explosion is the best possible outcome."

Me: "Umm, guys, it looks like the software needs at least 40 pounds on the robot"
Mentors: "WHAT?"
Me: "Yeah, look at it! #if, #define, #ifndef, #endif, #s all over the place!"

And my current autonomous code:

void Autonomous()
{
    // Declare victory
    bool victory = true;
}

Ironically, I get a compiler warning about an unused variable when I compile that

[Astarties]

The robot's not wrong, your drawing is wrong. - Said multiple times by the building group to the kid who drew the robot in autocad.

[WhiteShadow1474]

Me: It's so secure you can stand on it!
Advisor: You don't want to stand on that...

[FRC4ME]

Originally Posted by Radical Pi

Me: "Umm, guys, it looks like the software needs at least 40 pounds on the robot"
Mentors: "WHAT?"
Me: "Yeah, look at it! #if, #define, #ifndef, #endif, #s all over the place!"

Of all the "code has mass" jokes in this thread, this one is definitely the best.

While staring at an impressive custom circuit on a 4" x 6" PCB that another group built:
Student 1: "Wow, there are three 10A fuses, two 555 timers, a block of NAND gates, a quartz crystal, a PIC, some power MOSFETS, a wireless USB interface...what could this possibly do?"
Student 2: "Well, it could be a light."

(It was actually a motor controller.)

[Nadav Zingerman]

Programming to Mechanical: "The code has been ready for days, where's the robot?!"

Three days later:

Mechanical: "Okay, download the code."
Programming: "It's not ready yet."

[donnie99]

figure this one out, it was right next to the compressor, Close the dump valve DB! to the judges, dumb bell, try to figure the last part out

[Bjenks548]

"Tomorrow, just to spite you, I am going to leave a single chip on the field. You'll know it was me because it will be at the cross section of the center gray line, and the caution line."

[MagiChau]

Freshman: "I guarentee we will be driving the robot in 15 minutes."

Takes us like 2 hours to fix the cables connecting the jaguars for the CAN.

[Zuelu562]

Originally Posted by ZonChau

Freshman: "I guarantee we will be driving the robot in 15 minutes."

guarantees don't mean anything when you're dealing with FRC good sir

[Kyoshirin]

(Programmer/Electrical guy to be labelled as P)

P: Oh, yeah. I also need to fix a short. When the wires jiggle it makes these cool blue sparks! Hoho! They were teal that time!

P: Great. Now the laptop isn't even registering that the cRio exists. Oh, wait a second. *Holds up other-disconnected-end of tether*

P: Ugh! I downloaded the program AGAIN, but the number of errors DOUBLED! Whoops. I forgot to clear the log from last time. Nevermind, false alarm.

-needless to say, our base hasn't moved via controller yet.

[Radical Pi]

Mentor to me: We've dumped the idea of using a potentiometer on the ladder (our tube manipulator), as it was going to be too complex to implement. Instead, we'll be using a hybrid rotary encoder/potentiometer, along with a limit switch to define a home position.

Person 1: Is it just me or does the ladder look like a duck?
Me: Yeah, it kinda does
Person 2: Then let's name the robot "Quack Attack!"
Person 1: But what about the minibot? It needs a name too!
Me: How about "The Duckling"
Person 1: Quack Attack and The Duckling! Just like Batman and Robin!
*laughter around the room*

Another name that has been floating around for our robot is "Duck Norris"

Another suggestion for our robot's name has been "Ian", as that's the first name of our staff advisor and our head programmer. In the words of our head of electronics:
"Ian, go fix Ian. Ian broke it again."

[J93Wagner]

"Hey! Now we have a new way to change the lights!" - A fellow mechanical student who was commenting on how high our robot could reach.

And on a similar note:

Me -*raises lifter mechanism too high and knocks down a ceiling tile* "Huh. I guess we have another causality."

[BJC]

"Just stop looking for it and go make another one. Then you'll find it right after the other one's made" - About 10 people were looking for a special bracket for 40 minutes after it dissappeared. The day after (we had already made a new one) a Freshmen walks up to me. "Is this important? I found it on the table." *Facepalm*

"Ok, we are never working in the shop again." - Our sub team usually works outside of the shop next to the road. (Yes, there are roads inside Chrysler)

A: "Ok, we'll probably have the final claw for you by Saturday."
B: "Really!?"
A: "Well.. maybe the end of Saturday."