Designing Driver Controls - Dutton-Christian-Robotics/Learning-to-Code GitHub Wiki

would it be best for a particular robot function to have a separate control for each "state" or would it be best to toggle/cycle between them? (e.g. toggle between claw open or closed, cycle between preset stages for a lift)
how many digits does it take to exercise a type of control (e.g. with a tank drive you need two digits to drive and turn—in fact, you need two to just drive straight; Defender-style controls require just one digit)
Are there movements/actions that should be assigned "dead-man switch" style?