How to use this guide¶
The shape of a module¶
Every module page has the same five parts, so you always know where you are:
| Part | What it is | How long |
|---|---|---|
| Why this matters | Two or three sentences. What breaks in the real world if you do not know this. | 1 minute |
| Learn | The two to five best resources we could find, in order. Each one has a type, a time estimate, and one sentence on why it is there. | Varies; shown per item |
| Do | One to three hands-on checkpoints on real hardware. This is where the learning actually happens. | 1 to 4 hours each |
| Check yourself | A few questions. If you cannot answer one out loud, go back to the relevant resource. | 10 minutes |
| Go deeper | Collapsed by default. Optional extras for when you are curious or your job needs it. | Skip on the first pass |
Tags on resources¶
Each resource line looks like this:
- Video Title of the thing by Author ~45 min One sentence on why this one earned its place.
The tag tells you the format (Video, Article, Book, Course, Docs, Interactive, Tool). A Paid tag means it costs money; we only include paid items when nothing free is as good, and there is always a free alternative nearby.
Checkboxes¶
Click any checkbox to tick it. Progress is saved in this browser's local storage and nothing is sent anywhere. The home page shows a summary across all modules.
- Ticking a Learn item means you finished it, not that you opened it.
- Ticking a Do item means it works on your desk and you could explain how.
- If you fork the repository on GitHub, you can also tick boxes directly in the Markdown files.
Time estimates¶
Estimates are for a focused first pass by someone at the module's intended level. Videos are listed at their real length. Reading estimates assume you take notes. If something takes you twice as long, that is normal and not a signal to skip it.
Free first¶
Every module can be completed with free resources. Where a paid book is listed, it is because it is the best single reference on that topic and worth owning once you know you are staying in the field. Your library may have it.
When you get stuck¶
- Re-read the datasheet section. Really.
- Reduce the problem: fewer lines, one peripheral, a known-good example.
- Look at the signal with a logic analyzer or scope. Guessing is slower than measuring.
- Ask in a community listed in Module 20. Show what you tried.
- Only then ask an AI, and verify its answer against the datasheet. Module 18 explains why this order.