Classes and three small tested projects: the Phase 1 capstone.

1. 1.Problem Set 6, next problem

   CS50P Problem Set 6 (opens in a new tab)
2. 2.Test it against the spec examples

   Run every example from the problem page; it should match exactly.

3. 3.Commit what you did

   $ git add -A

   $ git commit -m "Week 4 mon: Problem Set 6, next problem"

   $ git push

Companion video

Python OOP Tutorial 1: Classes and InstancesCorey Schafer · Mon

1. 1.Python tutorial §5 Data Structures (docs.python.org), §5.1, 5.4, 5.5

   Python tutorial §5 – Data Structures (opens in a new tab)
2. 2.Commit what you did

   $ git add -A

   $ git commit -m "Week 4 tue: Python tutorial §5 Data Structures (docs.python.org), §5.1, 5.4, 5.5"

   $ git push

Companion video

Python OOP Tutorial 3: classmethods and staticmethodsCorey Schafer · Tue

1. 1.Exercism: 2 exercises

   Exercism – Python track (opens in a new tab)
2. 2.Commit what you did

   $ git add -A

   $ git commit -m "Week 4 wed: Exercism: 2 exercises"

   $ git push

Companion video

Python Tutorial: Type Hints – From Basic Annotations to Advanced GenericsCorey Schafer · Wed

1. 1.Work through: CS50P Week 8 – Object-Oriented Programming

   first ≈60 min

   Open (opens in a new tab)
2. 2.Work through: Missing Semester 2026 – Command-line Environment

   environment variables, ≈30 min

   Open (opens in a new tab)
3. 3.Do

   Type along; write down 3 questions you still have.

4. 4.Check you’re done

   Done when: Notes committed.

Companion video

CS50P – Lecture 8 – Object-Oriented ProgrammingCS50 · Thu

1. 1.Do

   BankAccount (deposit, withdraw, balance, error on overdraft) with 5 tests.

2. 2.Check you’re done

   Done when: Tests pass.

1. 1.Catch up first

   Finish anything unticked from Mon–Fri this week before stretch work.

   Week 4 sessions
2. 2.Then stretch work

   Bill-splitter command-line app with 5 tests.

1. 1.Start with 20 min revision

   Re-solve a Problem Set 4 problem from memory.

   CS50P Problem Set 4 (opens in a new tab)
2. 2.Work through: Missing Semester 2026 – Debugging and Profiling

   ≈30 min

   Open (opens in a new tab)
3. 3.Do

   budget_analyser: 30 fake rows in a CSV → totals per category → summary.csv, currency from an environment variable. Then start tracker-cli (add/list/complete items in JSON) on a branch.

4. 4.Check you’re done

   Done when: budget_analyser runs; tracker-cli add/list work with 4 tests.

5. 5.Commit

   mini/budget_analyser/, projects/tracker-cli/

   $ git add mini/budget_analyser/ projects/tracker-cli/

   $ git commit -m "Week 4: Two mini-projects"

   $ git push

1. 1.Do

   Finish tracker-cli (≥8 tests, README with 3 examples); open a pull request on GitHub and merge it; weekly review.

2. 2.Check you’re done

   Done when: PR merged; tests pass.

3. 3.Commit

   projects/tracker-cli/ (merged PR)

   $ git add projects/tracker-cli/

   $ git commit -m "Week 4: Capstone PR + review"

   $ git push
4. 4.Weekly review (last 30 min)

   3 wins, 3 confusions, 1 thing to re-learn – written at the bottom of this page and saved with your progress.

   Open the weekly review