

Software Revision Control systems are databases for storing computer software. FRC teams should also follow this practice. In professional software environments, the code is usually stored in a Revision Control System. And, if the code worked yesterday but fails today, you want to know what has changed. You might want to compare the code used in two different competitions. Also, you want to keep the history of the development.

So you’re developing code for your robot, but where should you store the master copy of that code? Keeping everything on a single laptop is a terrible plan you at least need backups, maybe multiple backups. Installing Java for FRC programming August 12, 2018.Creating Java Robot Programs with VS Code September 5, 2018.

Creating Java Programs with Eclipse October 21, 2018.Debugging: print statements and logging December 9, 2018.Debugging: Shuffleboard December 15, 2018.Creating Java Programs with IntelliJ December 27, 2018.Debugging: Java Remote debugging January 1, 2019.The Driver Station Log File Viewer February 15, 2019.Preparing for Competition February 23, 2019.Labiew Dashboard Camera Fixes March 11, 2019.Loop time override warnings March 12, 2019.FRC 2019 – Camera Best Practices April 4, 2019.Unit Testing Subsystems September 9, 2019.Unit Testing Commands September 16, 2019.Command-Based Robot Architecture December 14, 2022.Command-Based Programs with RobotBuilder December 20, 2022.Search for: Tags C++ Eclipse git IntelliJ Java Visual Studio Code Recent Posts
