[Beginner] · Want to learn something? Make a course.

The move

The vague version — “I want to get better at software engineering” — gives my brain nowhere to put the ambition. So it leaks: into comparison, into starting five things, into the feeling of being behind.

The fix is to convert the vague interest into a named course:

SWE 101.

Then define it properly:

  • Course objective
  • What the role actually involves
  • Skills required
  • Current strengths
  • Knowledge gaps
  • Modules
  • Scheme of work
  • Notes
  • Practice questions
  • Examples
  • Projects
  • Real-world application

The same frame works for anything: Manhood 101, Finance 101, Public Speaking 101, Robotics 101. It’s unconventional. It works anyway.

Why it works for me

The structure supplies exactly what the JAMB environment supplied (see How I Learn):

  • a target
  • a beginning
  • a progression
  • a syllabus
  • a place for notes
  • a place for questions
  • a place for practice
  • a way to measure progress

And it forces repeated exposure — reading, writing, questioning, practicing, revisiting — which is what actually moves a concept from “seen” to “mine”.

What it does not do

A course does not produce embodiment.

Learn → Understand → Remember → Practice → Reflect → Repeat → Embody

Finishing a syllabus means I’ve done the reading. It doesn’t mean I can do the thing. Every course needs a projects/application section or it’s a reading list wearing a syllabus’s clothes.

Anatomy

The fill-in version lives in COURSE-TEMPLATE. Copy it, don’t reinvent it each time.

A scheme of work in the JAMB shape — one subject per day, on a fixed rotation — is the default, not one-subject-forever and not everything-every-day.


Next: One Active Course — the rule that keeps this from becoming twelve courses.

Related: The Primetechie Path is effectively SWE 101’s scheme of work, already written. BUILD-PLAN is the same idea applied to writing this vault.

↑ Back to Learning — How I Learn