Skip to content

1.5 How to Run This Course

Courses don't fail because the material is too hard. They fail because life is busy and there was no system. This lesson gives you the system: the rhythm, the journal, the lane discipline, and the honest expectations that get you from here to a shipped capstone.

What you will learn

  • Set up the builder's journal you'll keep for the whole course.
  • Choose your lane and know when to switch.
  • Plan a realistic schedule you'll actually keep.
  • Know exactly what to do when you get stuck.

Builder principle

Use a repeatable pace and adjust it from evidence. A fixed weekly schedule does not guarantee a fixed finish date.

The builder's journal

Before anything else, create one place where the whole journey lives. Notes app, paper notebook, doc — the medium doesn't matter; the habit does.

It already has three entries if you've done the lessons so far: your time-eater list (1.1), your chatbot-vs-agent brief (1.2), and your three builds (1.4). From here, add after every lesson:

  • What I did — one line.
  • What surprised me — one line.
  • What I'd try next — one line.

Three short lines. By Chapter 11 this journal can supply raw material for a capstone build log, a portfolio story, or a client process explanation. Those artifacts support review; they do not guarantee a sale.

Meta move

In Chapter 5 you'll learn to make your journal agent-readable, turning it into memory your AI can use. Write it like a future teammate will read it. One will.

Choose your lane — and hold it

For the assessed route, read each lesson, complete one bounded practice artifact per track, and do every chapter checkpoint. "Try it now" repetitions and videos are optional extensions unless a checkpoint names their evidence. Add them when a concept is new or your checkpoint evidence is weak.

Your risk: Chapter 3 may require more time when the terminal is new. Plan an extra session, use the supported recovery or simulation path, and pause rather than treating a slower pace as failure.

Use the entry diagnostic and chapter checkpoints to decide where to skim. Still do the 1.4 build-list exercise; prior coding experience does not by itself demonstrate framing, tool-boundary, or verification judgment. Slow down wherever the evidence is weak.

Your risk: equating prior AI use with evidence on this framework. Measure behavior before and after instead of assuming either competence or improvement.

Switch lanes any time. Reading the other lane's tabs is encouraged — knowing how the other half works is part of the skill.

Choose a route and schedule

The course overview defines what each route includes. Use these ranges for calendar planning:

Route and weekly time Estimated calendar range
Reading/reference at 3–4 hours/week 3–6 weeks
Assessed practice at 3–4 hours/week 8–17 weeks
Assessed practice at 8–10 hours/week 3–7 weeks
Assessed practice + capstone at 3–4 hours/week 10–25+ weeks
Assessed practice + capstone at 8–10 hours/week 4–10+ weeks

At the end of Chapters 3, 6, 9, and 11, use a pause point: review scores and feedback, repeat the weakest essential task if needed, and revise the remaining calendar. Completing only Foundations or the reading route is a valid declared stopping point; record which route you completed.

Rules that keep people finishing:

  1. Schedule the sessions. Calendar, recurring, non-negotiable — like a class you paid for. (You did pay: with attention.)
  2. End every session mid-momentum. Stop while you know your next step. Blank-page starts kill streaks.
  3. Revise the schedule deliberately. A missed session is information. Move the date, narrow optional work, or take a declared pause rather than hiding the change.

When you get stuck

You will get stuck. Here's the order of operations:

  1. Read the error out loud. Half of all stuck-ness dissolves right here.
  2. Check the Glossary. Unfamiliar words masquerade as hard problems.
  3. Ask an AI with a sanitized error. Remove credentials, personal data, private paths, and confidential context first. Share the exact safe-to-disclose error plus what you were trying to do. Learning to get unstuck with AI is course material, not cheating.
  4. Step away for ten minutes. The shower has debugged more problems than any tool ever made.
  5. Ask the community. GitHub Discussions — someone has hit your wall before, and your question helps the next person.

Before you leave this chapter

  • Builder's journal exists with entries from 1.1, 1.2, and 1.4.
  • Lane chosen. Schedule on the calendar.
  • Essential route selected; optional videos and repeated builds marked separately.
  • Setup done — or scheduled for before Chapter 3.

Check your understanding

  • What are the three lines you write in your journal after every lesson?
  • What's your lane, and what is that lane's specific risk?
  • What are your route, weekly time budget, first pause point, and rescheduling rule?
  • What are the five steps of getting unstuck, in order?