Files
rootnode-academy/content/root/root-01-computing-linux-foundations/m01-how-computers-run-software/03-reflection.md
T
ced4568andClaude Sonnet 5 15b616274b feat(root01): author Computing & Linux Foundations, and the real 01->05 prerequisite chain
Adds all 6 ROOT 01 modules (how computers run software, the shell, filesystem navigation,
files & text, processes, users & permissions foundations), each with a real lesson,
demonstration/guided exercise, knowledge check where warranted, a hands-on Lab, and a
reflection — 35 activities, 29 new content files.

Adds 6 new hands-on Linux scenarios (linux-inspect-hardware, linux-shell-basics,
linux-filesystem-navigation, linux-files-and-text, linux-process-management,
linux-permissions-foundations) plus 2 MCQ scenarios, using the existing generic scenario/
validation engine (docs/ROOT_FOUNDATIONS_LAB_STRATEGY.md §1) — every one tested end-to-end via
the real scenario setup/validate API, including negative tests confirming they correctly FAIL
when not actually solved (e.g. the process-management scenario fails while the target process
is still running; the permissions scenario is tested against a real `su - labuser` denial).

Wires rootnode-linux-foundations-assessment (2 required + 4 random-draw scenarios) using the
existing Phase 3B assessment engine.

Adds a real, server-side ROOT 01->02->03->04->05 course prerequisite chain
(courses.prerequisites) — verified live on two students: one who completed ROOT 01 sees ROOT 02
unlock; a fresh student sees ROOT 02 correctly locked while 03/04/05 stay vacuously satisfied
(their own prerequisite courses are still empty). ROOT 06+ and the Capstone are unaffected.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
2026-08-26 12:59:52 -05:00

1.3 KiB

Reflection: You Just Looked Inside the Box

Reflection questions

  1. How close was your guess to the real numbers? What surprised you most?
  2. Name one thing you now understand about "the computer" that you couldn't have explained before this module.
  3. When you eventually run kubectl describe pod and see requests/limits for CPU and memory, what do you now expect those numbers to actually be constraining?

Real Ops takeaway

Every resource limit you'll ever configure — in Docker, in Kubernetes, in a systemd unit — is a promise about exactly the three things this module named: CPU, memory, and storage. You can't reason well about "why did my container get killed" or "why is my Pod stuck Pending" without this base model. This module isn't computer-science trivia — it's the vocabulary the rest of ROOT_ assumes you have.

This module is complete. Continue to the next module.

Instructor Notes

Discussion questions for a live classroom: question 3 is worth spending real time on — it's the first moment students connect this abstract lesson to something they'll type as a real command many courses from now. Naming that connection explicitly here pays off later.

Approximate timing: 5-8 minutes live discussion; 5 minutes self-paced writing.