[Sparkyshires]

the one position that began as an informal tradition about five years ago and is now almost a formal requirement is that the programming lead is the secondary driver. The reasoning behind this is that my coach wants to also have a programmer behind the glass, so he/she knows whats going on in the code if something goes wrong, and what better position to put him/her on than at control of all the safeties and overrides they built into it? I know that it's saved our butts on at least two counts, if not more.

But aside from that the human player is our manufacturing lead, and our main driver is our design and engineering lead, and our coach is an alumni/mentor.