Unit 08

Process, the Team, and the Season

By the end of this unit you can leave a shared laptop ready for the next person, judge borrowed or generated code against its requirement, and isolate a fault one layer at a time.

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 · 28 min read

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

69 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