Programming - TAMSFormers5212/TAMSformers-Database GitHub Wiki
Programming in FRC is both one of the most important parts of elevating a team's performance and also one of the most overlooked as a place for potential improvement. As a result, it is incredibly important to not only get programming done well, but also fast and effectively.
The programming subteam is made up of a programming captain, sometimes a special projects lead, and (hopefully) a bunch of juniors. The seniors main job is to train the juniors over the offseason so they can code and participate during the competition season. Each member of the programing team is expected to have their own laptop and be able to run code themselves. The programming team has two focuses during the year.
The first is to program the robot. This is usually led by the programming captain who decides on the structure of the code. Historically, the programmers have also participated in designing the robot (or at least deciding on an architecture/archtype), so they can start designing subsystems, state machines, and sensor locations earlier.
The second is researching new technologies or projects that can be added that year. This is mostly a offseason thing as using untested stuff on the competition robot doesn't end up well the first time. However, this is often a good side project for extra training and advancing our programming skills.
If there are more than a few programmers, it is a good idea to divide up into groups with individual focuses both for robot development and researching. We've never had this before, so whenever this happens, you can write more on this section.