Agenda

  1. Warm-up: Tech Headlines
  2. Discussion: Whose Code Is It β€” ownership, licences, and what you are allowed to reuse
  3. Consolidation: one design, taken all the way β€” classes, tests, and a paragraph defending the boundaries, starting from the revision list you wrote yesterday
  4. Look ahead: next unit, the containers themselves are the decision
  5. Last fifteen minutes: your Unit 1 milestone entry in your Code Journal, written here, with the unit’s own entries open beside you

Things to do before our next class

  • Bring a program of yours that uses a list where it should not.