Key Programming Best Practices
- Assume Nothing
- With code, you can never trust anything.
- Make sure your tests are complete
- Trust your instincts... if you think it could be a problem, it will be.
- Back Up Your Code
- GIT - most complete but takes some studying
- Google Drive or Drop Box - easy - get the job done, but you do the work
- Google Drive with Backupify - Small cost but automatic
- Carbonite or other backup - usually costs something
- Use Wireless Programming
- Allows you to download code faster
- Gives you great debug information
- Learn to use Log.d()
- When combined with Wireless program, saves you lots of time
- Gives you the information you need to figure out what is really happening in your code.
- Create a set of Utilities (OpModes) for Testing and NEVER Disable Them
- Test each wheel independently, slow speed, forward and backward
- Test each motor independently, slow speed
- Test each servo independently, slow speed
- Test each sensor independently
- Take a break every now and then... and remove yourself from electronic devices.
- There is no faster way to figure out what has been frustrating you for hours.
Beginning Programming for FTC
If you are just getting started with FTC, you will need to learn to program your robot. PCHS Robotics recommends that you use one of the Java-based methods for programming your robot, and avoid using the "Blocks Programming" method.We suggest using one of these methods:
- Android Studio (Windows-based: Best tool)
- On-Bot-Java (Will work if you don't have access to Android Studio)