[omalleyj]

I am glad to see there are so many suggestions for safe bahavior, not just "its impossible" posts, or "it has to be this <insert your favorite> way" posts.

Let me share some of mine (team programming mentor):

Every time the code changes retest.

Because getting practice field time is difficult we try to make sure the change seems to work by running it first in Test Mode, On Blocks, in the Pit. Then test on the Practice field in teleop and autonomous.

Test mode is a wonderful thing, you can test just subsystems without messing with your full auto or teleop code. This makes initial testing easier and more safe by omitting drive or mechanism code that isn't being tested.

Never enable the robot if you aren't looking at it (this is sometimes tricky, but do it). While the robot is enabled everyone in the pit should be eyes on the robot.

Announce loud and clear that the robot is about to be enabled, in which mode, the expected behavior, and likely bad behavior to watch for.

Always have your hand on the E-Stop.

Always disable as soon as you can and before anyone approaches the robot who isn't involved directly in the testing.

Rings of team members shielding the area is needed to prevent passers by from wandering in, it doesn't stop the robot getting out.

While I love people coming to the pits to visit, they should not be there if the focus isn't on greeting visitors. If everyone is wrapped up in fixing and testing its better to have them return later.