Clear layers
Each part of the code has one job. Only one layer knows which physical port a motor is plugged into, so swapping a motor is an edit in one file.
FTC · FTC Team 19859 · Open source
Robot code written for the next team
Quick
start.
FTC Team 19859's robot code, organised and documented so the next team member can pick it up.
4
Clear layers of code
6
Steps to bring up a new robot
5
FTC libraries built in
Every push
Checked automatically
- Area
- FTC
- Built for
- FTC Team 19859
- Status
- Open source
- Stack
- Java · SolversLib · Pedro Pathing · Limelight3A
What it is
What it
What it
is.
Every FTC team rewrites its code every couple of years, and almost never because the old code stopped working. It is because the person who understood it graduated.
Biozbuzz Quickstart FTC is FTC Team 19859's open-source robot code, organised so that the next team member can read it, change it and trust it.
How it works
How it
How it
works.
The reasons, written down
Every structural decision has a short written explanation, and a wiring map matches the code.
A checklist for a new robot
A six-step checklist brings up a new robot, and every change is checked automatically when it is pushed.
Try It
See it
See it
decide.
The six-phase checklist a new robot goes through. Each phase is gated: you cannot advance while a check in the current phase is still failing.
Phases
What I learned
What I
What I
learned.
Write for the person who was not there
The interesting challenge was not speed. It was making the code make sense to someone who was not in the room when the decisions were made.
Code only its author can maintain does not last
A codebase that only its author can maintain has a shelf life, not an architecture. Writing down the reasons is what keeps it usable after the people who wrote it have left.