Copy this whole file into wherever the course lives, fill it in, delete the italics. Don’t reinvent the shape each time.
101: Course Syllabus & Module Standard
Started:
Where the reps happen: <notebook / board / repo / stage / studio>
The self-study standard
Use the shared course standard for the teaching notes. It borrows the motivation, plain-language explanations, and visual steps of the data-structures modules, then adds the missing bridge to independent work.
For each module, define:
- Starting knowledge and outcomes — explicit prerequisites, not a promise of zero background; what I will be able to explain and do.
- The mechanism — one concrete problem, terms introduced as needed, a state-by-state worked example, and why the steps work.
- The practice — predict → reconstruct with the example closed → make a guided change → implement or solve a new variation independently.
- The feedback — runnable checks or an assessment rubric, boundary cases, and hints/answers separated from the attempt.
- The finish line — a demonstrable artifact and the next lesson it prepares me for.
Use code, diagrams, proofs, or physical experiments according to the subject. Big-O tables and Python implementations are not requirements for every kind of course. Clearly distinguish runnable code from fragments, and provide setup and safety limits for experiments.
This template plans my learning. The shared standard governs how the lessons teach it; neither is evidence that I’ve learned the subject yet.
1. Objective
One sentence describing what I will demonstrate, not just what I will read. JAMB’s was “score above 300” — that specificity is the point.
2. What this actually involves
If it’s a role or craft: what does the person who has this skill actually do all day? Not the job title — the tasks.
3. Skills required
The real list. Break it down until each item is something that could be practised on its own.
4. Where I’m starting from
Current strengths:
Knowledge gaps:
Be honest here. The gaps section is what the modules get built from.
5. Modules (University Lecture Order)
The syllabus. Numbered, in reading/doing order — the same convention as the rest of this vault, so the order shows up in the file tree.
| Module | Prerequisites | Explain / demonstrate | Independent artifact or problem | Done when |
|---|---|---|---|---|
| 01 — Foundations | ||||
| 02 — Core mechanism | ||||
| 03 — Application |
Mark optional extensions explicitly. The next module should depend on a skill practised in the previous one, not just vocabulary mentioned there.
6. Scheme of work
Which module on which day. One subject per day on a fixed rotation, not everything every day.
| Day | Focus |
|---|---|
| Mon | |
| Tue | |
| Wed | |
| Thu | |
| Fri | |
| Sat |
7. Notes
Where the physical notes live. Physical first — the digital version is the synthesis step, written after reconstruction, not before. See the loop.
8. Practice
Problems, drills, exercises. Put the relevant practice immediately after the lesson that prepares me for it; link existing exercise banks instead of duplicating them. Keep hints and solutions separate from my attempt.
The worked-solution rule: study 1–2, extract the pattern, close them, solve new ones cold. Never copy a third.
9. Projects / real-world application
Required, not optional. A course with no projects section is a reading list. What does “I can actually do this” look like, concretely?
10. How I’ll know it’s working
Measurable target + visible progress. What’s the board? What gets ticked?
Review log
Date · module attempted closed-book · what I could explain/build · where I got stuck · what changes. Distinguish a tested example from a lesson I’ve actually studied successfully.
Software engineering
Infrastructure & security
Computer science
Hardware & engineering