Team Programming - Dutton-Christian-Robotics/Learning-to-Code GitHub Wiki

As programmers, we function as part of a team—with the shared goal of making our robot as functional and reliable as possible.

There are important differences between being a solo programmer and part of a team. Because what we do in programming needs to be much more precise and consistent than in anything else we do in life, it's important that we all agree on and use a consistent set of terms.

• Motor and sensor names. These are established when the robot controller is configured. It's important that everyone understands how functional parts of the robot are labeled—not only "what" they are labeled but "how" they are labeled. At some point it would become very confusing and problematic if one motor was named "back_left_motor" and another was named "right_front_motor" (notice the order of components of the name). No one should have to guess what something is called.
• Variable and class names. Standard Java style has class names capitalized and variables names in camel case, starting with a lowercase character.

As we get closer to programming actual robots (whether the testing robots or the competition robot), it will become important that we know who is responsible for writing which code and for making sure we don't accidentally overwrite each others' code. Part of this will involve our use of GitHub repositories.