Week 2 of 21 · Mon 23 Nov – Sun 29 Nov 2026
Phase 1 · Mac, Git and Python from zero (Weeks 1–4)
16:15–17:00 after you wake properly. One untimed problem and revision – never new material.
Mon · 23 Nov
16:15–17:00
How to do it
0/3 steps1.Problem Set 1, problem 3
2.Test it against the spec examples
Run every example from the problem page; it should match exactly.
3.Commit what you did
$ git add -A$ git commit -m "Week 2 mon: Problem Set 1, problem 3"$ git pushTue · 24 Nov
16:15–17:00
How to do it
0/3 steps1.Problem Set 1, problem 4
2.Test it against the spec examples
Run every example from the problem page; it should match exactly.
3.Commit what you did
$ git add -A$ git commit -m "Week 2 tue: Problem Set 1, problem 4"$ git pushWed · 25 Nov
16:15–17:00
How to do it
0/3 steps1.Problem Set 1, problem 5 + 1 Exercism exercise
2.Test it against the spec examples
Run every example from the problem page; it should match exactly.
3.Commit what you did
$ git add -A$ git commit -m "Week 2 wed: Problem Set 1, problem 5 + 1 Exercism exercise"$ git pushLearn on Thursday, build Friday to Sunday. Friday flex is catch-up first, then stretch work.
Thu · 26 Nov
14:30–16:30
How to do it
0/4 steps3.Do
Watch and type along; write 5 loop drills of your own (FizzBuzz, digit sum, count vowels…).
4.Check you’re done
Done when: Drills committed with asserts.
Short on sleep? Do the minimum version: Lecture only. Let the next buffer week absorb the rest.
Fri · 27 Nov
09:00–10:30
How to do it
0/3 steps2.Do
Solve 2 problems.
3.Check you’re done
Done when: Both pass their spec examples.
Short on sleep? Do the minimum version: 1 problem. Let the next buffer week absorb the rest.
Fri flex · 27 Nov
10:45–12:15
How to do it
0/2 steps2.Then stretch work
4 Exercism exercises; rewrite 2 earlier programs without looking.
Sat · 28 Nov
09:30–12:30
How to do it
0/5 steps1.Start with 20 min revision
Re-type one Problem Set 0 solution from memory.
3.Do
Remaining Problem Set 2 problems; Week 3 lecture; first 2 Problem Set 3 problems.
4.Check you’re done
Done when: Problem Set 2 complete; 2 Problem Set 3 programs survive bad input.
5.Commit
cs50p/ps2/, cs50p/ps3/
$ git add cs50p/ps2/ cs50p/ps3/$ git commit -m "Week 2: Problem Set 2 + exceptions"$ git pushShort on sleep? Do the minimum version: Problem Set 2 complete. Let the next buffer week absorb the rest.
Sun · 29 Nov
10:00–13:00
How to do it
0/5 steps2.Do
Remaining Problem Set 3 problems; break one on purpose and find the bug with breakpoints; weekly review.
3.Check you’re done
Done when: notes/debugging.md explains one bug found with the debugger.
4.Commit
cs50p/ps3/, notes/debugging.md
$ git add cs50p/ps3/ notes/debugging.md$ git commit -m "Week 2: Debugging + review"$ git push5.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.
Short on sleep? Do the minimum version: 1 problem + review. Let the next buffer week absorb the rest.
The last 30 minutes of Sunday. Saved with your progress.