Unit 08

Process, the Team, and the Season

By the end of this unit you can leave a shared laptop in a state the next person can pick up, get a library to do something its documentation never demonstrates, judge borrowed or generated code against the requirement it was meant to meet and say where it came from, put a number on a mechanism before it gets built, isolate a fault one layer at a time and write down what it turned out to be, and move a dependency without breaking the merge.

Robotics Programming · members' unit

Process, the Team, and the Season is behind a locked door

Units in Robotics Programming are for people taking the course. Getting in takes a link or a key — signing in on its own doesn't do it.

What's in this unit · 24 min read

  1. The person who sits down next
  2. What a commit message is actually for
  3. Pull before you start
  4. The docs never show your exact case
  5. Reading toward a goal, not reading through
  6. Extending what last season left you
  7. Code that looks right
  8. Check it against the requirement, not against your taste
  9. Say where it came from
  10. A number before a mechanism
  11. Two designs, one set of constraints
  12. Four layers, one symptom
  13. The ladder, and why the order is not optional
  14. The tool that touches nothing
  15. A control is a fact about a date
  16. Retracting a lead, in writing
  17. A checker has three verdicts, not two
  18. Write the hour down
  19. Two directions, two mechanisms
  20. One at a time, and build in between
  21. A bump can break what no compiler sees
  22. Keep the merge boring

31 quick checkscode exercises

1 Sign in

With your school Google account. This is how your work reaches the gradebook — it doesn't open the unit by itself.

2 Get in

Open the class link your teacher posted — that's the usual way, and it enrolls you on the spot. Or paste an access key if you were handed one.

A key unlocks this browser and keeps your progress here; signing in keeps it with you across devices. Either way the key itself is only ever checked as a hash. Manage all of this on your account, read what signing in stores, or go back to Robotics Programming.

Sources

  • GA-Moonshots — Artemis, the team base code — architecture.md, diagnostics.md, updating-from-upstream.md, issue-log.md, AGENTS.md
  • GA-Moonshots — Ganymede, the previous season — the known-good control this unit keeps returning to
  • Gilmour Academy Competitive Robotics — Software Team course notes — the chapters these standards were harvested from