The live register. One active course; everything else is parked, not abandoned.
Rule: One Active Course.

Active

SWE 101 — building a production codebase, and graphs under pressure. 8 weeks, from 2026-10-05. Reps live in the physical notebook.

Target: a remote full-stack / AI-engineering role. Full-stack and AI engineering converge on one profile — a TS full-stack engineer who ships AI product features and can prove they work — so they are one prep surface, not two.
The series: SWE 101 (8 weeks) → SWE 102 — AI engineering (6 weeks) → SWE 103 — systems and interviews (11 weeks). Run one after another, never in parallel — 102 and 103 are queued, not active. Each week has four lanes — DSA, Apply, Build, Learn — dropped from the bottom when a week collapses.
Restructured 2026-10-01: the first version (a 28-week hire track beside a 30-week scheme, started 2026-08-21) wasn’t followed and contradicted itself. It’s in the archive.
The notebook: method — the vault is the library; the notebook is reconstruction and reps only. Sections are numbered course.week (101.3).

Why this one: the near-term mission is financial capability through software engineering. Not because the others matter less — because this one funds the others.

Parked — real, waiting their turn

Not abandoned. Not now does not mean never.

  • Java / Spring backend — real evidence (direct-debit sandbox, record-id-generator, RabbitMQ, JVM concurrency), deliberately off the CV for this job search. Parked 2026-08-21: a CV aimed at four roles reads as aimed at none.
  • Mobile — React Native via arete. Parked 2026-08-21, same reason.
  • Embedded / hardware — the IoT bridge PCB is real and rare. Parked 2026-08-21, same reason.
  • Robotics 101 — notes already exist (robotics, control theory) but marked [reference]; the debt is reps, not notes
  • Music 101
  • Art 101 — drawing
  • Public Speaking 101
  • Podcasting 101
  • Finance 101
  • Manhood 101
  • Ministry
  • Travel
  • Reading — the exception: this one runs continuously as the low-pressure exploration space, not as a course. See Attention and Stillness.

Parking lot — things that grabbed me

Captured so they stop shouting. Date them. Most will never become courses, and that’s the correct outcome.

DateWhat caught my attentionStill interesting later?
2026-08-23Game development — one of the three original reasons for tech. Map now written: game-development/Yes. Next action is a game jam, not a course — 48 hours tests it properly
2026-08-23Embedded software engineering — wants to get into itYes, and you’re closer than you think: PCB + firmware already exist. See kinds of SWE
2026-08-23Data centres / infrastructure careerYes — and it’s adjacent to, not divergent from, the current track. route written
2026-08-23Desktop applications — “how do I make mine”Mild. Map written; a Tauri app is a weekend if it ever matters
2026-08-23Finance, tax, entrepreneurship — “to become a better person”Yes, and genuinely important — but explicitly deferred by you in the same breath. Not a tech course; needs its own shape
2026-08-23Manufacturing business — “can I start one”Unknown, and under-specified. This is a business question, not a learning one. Would need a real problem and a real market before it’s a course
2026-11-12The knowledgebase as an interactive learning platform: change it from static notes into something you learn with. An AI tutor teaches from the notes, asks and answers questions, quizzes, critiques explanations and sets build tasks, while I write the code myself. The vault stays the source of truth.Yes. Try it by hand first: one topic, the vault notes as the source, a chat in sparring mode. Build a platform only once the by-hand version has worked for a few weeks

Before adding anything to “Active”: is the current one done, or genuinely being retired? Two active courses is the failure mode this file exists to prevent.


Note added 2026-08-23

Six interests surfaced in one session, alongside “I’m thinking of so many things I can do to make a future-proof career.” All six now have written maps in the vault, and none is an active course. That’s the correct outcome and it’s what this file is for.

The maps cost a session. Starting them would cost the job search, which is the thing currently funding everything else — and the parking decision of 2026-08-21 (Java, mobile, embedded, robotics all parked, “a CV aimed at four roles reads as aimed at none”) was made forty-eight hours before this list appeared.

Notes are not commitments. They’re there so that when one of these comes round properly, the ground is surveyed. → One Active Course

↑ Back to Learning — How I Learn