A personal, evidence-based notebook for computer engineering coursework and self-study. It keeps small programs, lab notes, decisions, mistakes, and next questions together so progress can be reproduced instead of remembered vaguely.
This is a learning journal—not a claim that every roadmap topic is already mastered, and not a production library.
| Area | Evidence | Status |
|---|---|---|
| C++ console fundamentals | 3 compile-tested examples | Completed |
| Term 1 reflection | journal entry | In progress |
| Digital logic | study queue | Planned |
| Embedded systems | study queue | Planned |
| Computer architecture | study queue | Planned |
examples/cpp/ Small programs that compile in CI
journal/ Dated reflections and experiment records
notes/ Topic notes backed by examples or references
projects/ Larger project briefs and future build reports
ROADMAP.md Planned topics, with no completion claims
You need CMake 3.20+ and a compiler supporting C++17:
cmake -S . -B build
cmake --build build
ctest --test-dir build --output-on-failureCI runs the same build and output checks on Linux and Windows. A green badge means the checked-in examples compile and match their expected output; it does not substitute for hardware experiments or deeper understanding.
Each substantial entry answers:
- What was I trying to learn?
- What did I build or measure?
- What evidence shows the result?
- What failed or surprised me?
- What is the next smallest question?
The entry template keeps future updates consistent.
This is primarily a personal record, but corrections and focused learning suggestions are welcome. Please avoid submitting completed coursework on someone else's behalf. See CONTRIBUTING.md.
Code and documentation are available under Apache-2.0.