Lesson 46: Code Review and Team Workflow
Robot code is team code. Code review and workflow are how a programming team keeps one student's quick fix from becoming next week's mystery bug.
Use Branches
Create a branch for each feature or fix. A branch gives you a place to work without breaking the main robot code.
git checkout -b intake-state-machine
Open Pull Requests
A pull request shows what changed and gives teammates a chance to ask questions before the code is merged. It should explain the goal, the files changed, and how the code was tested.
Review for Robot Bugs
Good review is not about sounding smart. Look for practical robot risks:
- Can two classes command the same motor?
- Are port numbers and CAN IDs correct?
- Does the mechanism stop if a sensor fails?
- Are constants named clearly?
- Was the code tested on hardware, sim, or both?
Write Team Conventions
Agree on names, folder structure, formatting, and commit habits before build season gets intense. Conventions remove small decisions so students can focus on the robot.
Share Knowledge
If only one person understands a subsystem, the team has a risk. Pair program, review code together, and leave notes that help the next student pick up the work.
Practice
Write a pull request checklist for your team. Keep it short enough that students will actually use it before merging code.