Quote:
Originally Posted by arhajder
I believe ideally it should be the programmer.
|
The funniest part about this statement is that on my team, the lead programmer (different person each year) has been the driver for the last 2 years. For us, it is most likely because the programmer is normally on the sticks the most before the drivers test working out bugs in the code.
To add to the discussion, we give everyone about 2-3 minutes on the sticks after the robot is completed and then have them drive a course in the classroom with me on the disable switch. The mentors then judge them on skill and it goes from there. We have decided that it is best to just decide who the driver is, and then spend the rest of our available time having them practice driving and working with the arm man.