Things to experiment with once the code is good

[danielbrownmsm]

• NetworkButton
• Filesystem
• DriverStation
  • Get match time - post match time to Shuffleboard
  • Get joystick type - make sure the joysticks are in the proper mode (x or d)
  • Get count of joysticks - make sure both sticks are plugged in
  • throw warning/error - to force the drivers to listen to the code when they're breaking something
• Preferences - store tuning values here? (this is actually persistent, unlike Shuffleboard

[danielbrownmsm]

• Re-writing the subsystems to be passed the motors and whatnot instead of declaring them inside themselves. This way we can use fake data and stuff.
• checking out WPILib's testing suite, because they might know what they're doing so we should maybe consider using what other programmers wrote with programmers programming better in mind