Buffer week 17 · Mon 8 Mar – Sun 14 Mar 2027
Buffer 3 of 3 · catch up, consolidate, rest
16:15–17:00 after you wake properly. One untimed problem and revision – never new material.
Mon · 8 Mar
16:15–17:00
How to do it
0/3 steps2.Re-solve it untimed and AI-free
From a blank file, without looking at your old solution.
3.10 min of reviews/relearn.md
Tue · 9 Mar
16:15–17:00
How to do it
0/2 steps2.Re-solve it untimed and AI-free
From a blank file, without looking at your old solution.
Wed · 10 Mar
16:15–17:00
How to do it
0/3 steps2.Re-solve it untimed and AI-free
From a blank file, without looking at your old solution.
3.Or rest
Rest is a valid use of a buffer week.
Learn on Thursday, build Friday to Sunday. Friday flex is catch-up first, then stretch work.
Thu · 11 Mar
14:30–16:30
How to do it
0/2 steps1.Do
Finish the oldest unticked ‘done when’ check from Weeks 14–16 (micrograd, PyTorch, transformers, LoRA).
2.Check you’re done
Done when: One more check ticked.
Short on sleep? Do the minimum version: One item. Let the next buffer week absorb the rest.
Fri · 12 Mar
09:00–10:30
How to do it
0/2 steps1.Do
Next unfinished item. If nothing is left, derive backprop for a 2-layer MLP on paper and check it in code.
2.Check you’re done
Done when: Check passes.
Short on sleep? Do the minimum version: Paper only. Let the next buffer week absorb the rest.
Fri flex · 12 Mar
10:45–12:15
How to do it
0/1 steps1.This block
If you’re caught up: a 30-min call with your P5 user. Write down the words they use for the problem; they go into your README and demo.
Sat · 13 Mar
09:30–12:30
How to do it
0/5 steps1.Start with 20 min revision
Explain what LoRA trains and what it freezes.
3.Do
Turn your user’s 20 real questions into evals/p5_questions.jsonl, each with the expected answer and its source document. Agree what ‘good’ means: correct, cited, and saying ‘I don’t know’ when it should.
4.Check you’re done
Done when: 20 graded questions committed.
5.Commit
P5 evals/
Short on sleep? Do the minimum version: 10 questions. Let the next buffer week absorb the rest.
Sun · 14 Mar
10:00–13:00
How to do it
0/3 steps1.Do
reviews/phase4.md; update relearn.md; plan Weeks 18–21 around your user’s brief.
2.Check you’re done
Done when: Review + plan committed.
3.Commit
reviews/
$ git add reviews/$ git commit -m "Week 17: Phase review + plan"$ git pushShort on sleep? Do the minimum version: Review. Let the next buffer week absorb the rest.
The last 30 minutes of Sunday. Saved with your progress.