[RoBoTiCxLiNk]

This year, at our first regional, my biggest mistake was. It wasnt even my fault but what happened is that me (lead and only programmer) and the only other person on the team who knows what 'program' is, were sitting in the pits writing autonomous code. After our last match of the day, I assumed the kid would be alright, seeing as how he might occasionaly be an airhead, he can wield anything (be it hammer, keyboard, crimper, you name it) and instantly look like hes meant for it. looking over the code that night in the hotel, I cleaned up much of the teleop code we had (under the drivers specifications), and didnt think about looking at the auton. the next day, in our first match, i looked at the program while waiting in line for our robot to be set up on the field and notice he had a very buggy piece of autonomous in the default case. asking him about it right there (me and him are the drivers), he said he couldnt get it to download, so i wasnt worried. After we set up the robot and were waiting in the drivers area, waiting for the countdown ("red alliance, ready? blue alliance, ready? GO!). All of a sudden our bot (on a far side) just zooms out of its starting position in a nice arc all the way across our half of the field and makes it to the robot across from us (which also had autonomous, but worked) and cuts it right off, slamming into our side and messing both our autonomous up. after the switch to teleop, our robot was just stuck spinning in circles in and out of the lane, continually getting lane violations. all because a bug went achoo, and changed a variable that diverted the initial autonomous switch case.