As long as we are being poetic:
The Drive sub-team is by the far most abused and neglected of sub teams, so much so that many teams fail to consider it as a proper sub-team. While some programming teams may state they are given insignificant time, a mere 6 hours, we must remember that even they at least had that time, were some drive teams get only 24 minutes total.
How do we rectify this injustice? A modest proposal; one that, while it share not the same satirical subtilties of Swift, does share the simplicities. Build, wire, and program the entire drivetrain day 1 of build season.
Now, some may argue that 1 day is much too short to assemble a drivetrain. May I remind you that some teams have taken apart and reassembled an entire drivetrain between matches. If you can not assemble within the time of Dean’s declamation, then you dare fate to strike at the most inopportune moment. Train your team for such a task.
Some may argue that design plays an integral factor in establishing your drive base. May I propose the 3 reasons you should choose a specific drive base?
- It’s the drive base you know how to build the best.
- It’s the drive base you know how to program the best.
- It’s the drive base you know how to drive the best.
There is nary a game that changes any of the above factors. Thus, I propose that the above be decided before the season. Drive’s like Swerve and West Coast can easily be modified to many dimensions. Think of the time one can save by having your drive done day 1 instead of 21. Much needed time can be spent on intake and scoring mechanisms, which lead to much higher reward for less work.
Finally, if the drivetrain is done day one, then it reduces the strangle hold mechanical often has over programming and drive team. Rather than mere days designated for these disregarded disciplines, and entire season could be spend sharpening skills. Every sub-team is given equal opportunity to perfect their craft.
If any sub-team’s actions result in robot being in a non-working state, it is everyone’s first priority to make sure it is working by the start of next meeting.
I may not be able to state what the perfect driver is, but the above is one way to work towards achieving one.