This is a typical scene in a FRC pit: The programmer sitting on something trying to figure out why the heck the motors are wired wrong, while everyone else sits around waiting for the electronics person to get to the pit.
Here we see the programmer in his natural habitat. Oh look! Looks like he has been spotted by the drive team! Fearing for his life, the programmer grabs a near by laptop and begins typing senselessly into it. This is very similar to that of the North American possum playing dead to deter predators. It isn’t too long before the drive team is called to a match, very well saving the programmer. It looks like the drive team will just have to run that new auto in a match.
As the kid in the background looked into his magic spool of white 3D printer filament, spinning it in his hand three times over, that he realized their bot is overweight by about 3000 lines of unneeded special drive code.
Classic inspection photo:
The pit crew skeptically reviews their robot, one nervously spinning that light strip they removed to save weight.
In the background, the programmer writes the consistent ‘smoother drive code’.
The programmer in his natural habitat: Field side at a competition, with way too many bugs to fix. His teammates stalk him, oblivious to his total lack of progress.
Everyone assumes the programmer is writing a program for the robot, but he is actually testing the spinning code for the coil of wire his teammate is holding.
Programmer thinking: Man this game is great. No randomization to worry about, no vision targets to track, no articulating arms. I could program the whole match in autonomous. I bet we wouldn’t even need a driver. Then that’d make my code the driver. Which is like I’m the driver. That’d make me one of the cool kids. Alllll riiiiight!