|
Re: How is your team picking it's drive team?
Usually one of our drivers is a programmer (but it could be anybody,) because their task is to mesh our drive code with the new, season code (driving, mechanisms, etc.) They tend to have a better, general knowledge of the robot as a whole, and have consistent training with driving the robot and working the mechanisms together. (But again, it could be anybody.)
The other driver could be anybody, but in the past it tends to be the second programmer, for the same reason as listed above. This year it is a little different, because our program duo graduated, so they cannot be on the drive team. We're probably going to hold tryouts to choose the second driver.
Justin Montois is correct, as well. Teamwork is the number one component you need on a drive team - everything else, in truth, comes second.
__________________
"If you want your children to be intelligent, read them fairy tales." - Albert Einstein
|