Post

Periodic-Oriented Programming for FIRST Robotics

A longtime FIRST Robotics mentor argues for simple, periodic control loops instead of spreading robot behavior across a command scheduler. Each subsystem owns its hardware and applies outputs and safety constraints in one place on every tick; operator and autonomous logic set desired states.

The author says this reduces hidden state, conflicting hardware writes, and debugging complexity for most teams. In the Lobsters discussion, another mentor agrees it fits many teams but notes that sensor availability limits state-based control, while sophisticated autonomous robots can benefit from command-based structure.