Postscript: Make the Route Your Own System¶
A public navigator can provide candidate routes, reviewed resources, and common quality standards, but it cannot choose your long-term objective. An effective route changes with foundations, time, equipment, and interests. What you maintain is not a permanent schedule; it is a learning system that can observe itself, correct errors, and continue operating.
This is not a checklist to finish¶
Course count creates an easy sense of motion without proving capability. Keep one primary problem, one mainline course, and one checkable artifact in each stage. Alternatives replace a mainline that does not fit current constraints; supplements repair a defined gap. They should not accumulate automatically into a longer plan.
If a project, exam, derivation, or measurement already demonstrates a capability, skip redundant material. If a prerequisite blocks the current task, step back only far enough to repair it instead of restarting the entire discipline.
Maintain three ledgers¶
Evidence ledger¶
Record what was actually completed: representative exercises, derivations, code, simulations, raw data, design files, test results, and retrospectives. Every artifact should identify versions, parameters, and acceptance methods. Organize it with the Project Evidence Package.
Time ledger¶
Record planned and actual time, separating instruction, practice, debugging, projects, and writing. When the difference remains substantial for two weeks, revise future estimates instead of hiding a planning error with willpower. Getting Started provides a four-week cadence.
Risk ledger¶
Record electrical, mechanical, thermal, optical, chemical, data, and licensing risks together with controls. When equipment ratings, supervision, or operating limits are unclear, remain with simulation or a verified low-energy platform. Every physical activity should first pass the boundaries in Laboratory Safety.
Review the route every four weeks¶
Answer only five questions:
- Which artifact can another person inspect independently?
- Does the largest blocker come from concepts, mathematics, tools, feedback, time, or equipment?
- Which material solved the problem, and which material merely added switching cost?
- Which single goal, mainline, and artifact remain for the next four weeks?
- Which risks, costs, or access conditions have changed?
Write the answers on one page and update your stage on the Global Roadmap. Expand the plan only when evidence or constraints change.
When to pause, replace a course, or change direction¶
Pausing is not failure. Adjust actively when these signals appear:
| Signal | First action |
|---|---|
| Minimum exercises remain incomplete for two weeks | Narrow scope and inspect prerequisites and feedback |
| Video and reading increase while output stays empty | Stop new content and complete one verification task |
| Access, language, or cost does not fit | Choose an alternative within the same track |
| Project risk exceeds facilities and supervision | Switch to simulation, public data, or a lower-risk task |
| Interest in the direction’s central questions remains low | Finish the current minimum loop, then sample another direction |
| Health or life constraints cannot sustain the plan | Reduce load and preserve a minimum sustainable cadence |
When replacing a course, retain completed evidence and the error log. A switch does not mean starting from zero.
How to contribute¶
High-value contributions are not limited to new courses. Broken links, changed access conditions, inaccurate prerequisites, translation drift, unclear safety boundaries, and missing reproduction steps all deserve correction. Before submitting:
- prefer primary course or institutional pages;
- separate facts, personal experience, and maintainer judgment;
- update Chinese and English meaning together;
- do not submit restricted materials, personal data, or credentials;
- run the relevant checks described in the Contribution Guide.
A dated correction with evidence and limitations is more valuable than a large set of unverified links.
Long-term quality standard¶
The same questions apply in every direction:
- Can you explain it? State the model, assumptions, units, and applicability.
- Can you calculate it? Complete a representative derivation and check scale, signs, and residuals.
- Can you implement it? Build code, simulation, or a physical design within an appropriate safety boundary.
- Can you verify it? Create feedback through solutions, tests, a second method, or measurement.
- Can you reproduce it? Another person can obtain the same conclusion or identify the source of a difference.
- Can you communicate it? Figures, tables, prose, and design review make the conclusion inspectable.
When one dimension remains absent, reflect it in the next cycle. The Practice Guides provide the corresponding methods for tools, records, and communication.
Next action¶
If you are beginning, run the four-week launch. If the common core is in place, select a direction from Learning Routes. If mathematics is blocking progress, use EE Mathematics Foundations or Advanced Mathematics for EE to repair only the module needed now.
Do one thing today: write down one checkable artifact to deliver in the next four weeks, then remove every temporary course that does not support it.