|
Re: Should a programmer be a driver too?
Drivers for the Thunderchickens don't have very many rules. Our biggest one is NO drivers in the pit. I'm not sure how it's working out this year, because I've noticed our driver is a high up (if not lead) programmer, but this has always been a virtue. Like you said, the driver's job is to be the driver. That includes doing personal scouting of other teams, watching other teams' driving styles, strategy meetings before each match, as well as often being the personal ambassador to other teams. Those are enough responsibilities on their own. When they start having the pressure of elims plus having to fix the code at blazing speeds, many people will break.
That being said, if they really are your best driver, then it's worth it to give a try. I just feel that it is a level of stress that is often tough to tackle on its own, without added robot maintenance stresses.
__________________
VEX Robotics Marketing Manager
ThunderChicken driver '07-'08
Robowrangler '13-present
FIRST in Michigan, VEX Worlds, and FIRST in Texas MC/Game Announcer '08-present
|