Should a programmer be a driver too?

[dtengineering]

Regardless of who is the primary driver, I think it is important to have at least one software expert and one hardware (mechanical stuff) expert on the drive team. The software expert can download and modify code while waiting in Queing, while the hardware person can take responsibility for last minute fixes and adjustments.

Since we normally use students in the coaching role (and if you want to discuss that, do it in an exisiting thread... I'm not offering a value judgement here, just stating a fact) that makes it easier for us to cycle through different people in different roles.

I try to always make sure that we have at least two people who can drive the robot competitively... and at least one of them will be someone who will be returning the following year. We will often put the "junior driver" in with the lead driver as coach once or twice per regional, and will cycle other team members through other positions so that many people get a chance to be on the field.

But always, always, always, there will be at least one person who knows the software (often the lead programmer) and one person who knows the mechanial systems (often the lead builder/fixer) as part of the team.

Jason