Chief Delphi - Should a programmer be a driver too?

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)

- Team Organization (http://www.chiefdelphi.com/forums/forumdisplay.php?f=86)

- - Should a programmer be a driver too? (http://www.chiefdelphi.com/forums/showthread.php?t=75428)

Re: Should a programmer be a driver too?

over the past for years for 1807, i have been one of the drivers, as well as being the lead builder on our team. this has proved to be very handy when something goes wrong with our robot, and we only have a few minutes to fix it. also i have done the electrical work, which was one of our main problems this year, as pwm cables fell out often (fixed with a lot of tape)

we always have two mechanical people, our programmer (singular), and one of two coaches on our drive team. i think it is essential that teams have drivers that can not only drive very well, but can also fix the robot quickly under pressure.

Re: Should a programmer be a driver too?

Quote:

Originally Posted by dtengineering (Post 838750)

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.

100% agreed.