From shell to systems.

Shell navigation, paths, permissions, and a safe lab environment.

Make it tangible: Create a Linux lab, map its filesystem, and explain file permissions.

Learning loop: study → experiment → record evidence → explain in your own words.

Pipes, redirection, signals, process trees, and job control.

Make it tangible: Trace a command pipeline and document how its processes stop.

Learning loop: study → experiment → record evidence → explain in your own words.

System calls, user and kernel space, scheduling, and context switches.

Make it tangible: Trace a small program and explain the boundary it crosses.

Learning loop: study → experiment → record evidence → explain in your own words.

Virtual memory, paging, filesystems, mounts, and storage tools.

Make it tangible: Compare process memory observations and filesystem usage.

Learning loop: study → experiment → record evidence → explain in your own words.

Service lifecycle, logs, resource usage, and repeatable diagnosis.

Make it tangible: Break a disposable service, diagnose it, and write a recovery note.

Learning loop: study → experiment → record evidence → explain in your own words.

Addresses, subnets, routes, interfaces, and the TCP/IP model.

Make it tangible: Draw the route between a client, router, and server.

Learning loop: study → experiment → record evidence → explain in your own words.

Connections, ports, reliability, and transport trade-offs.

Make it tangible: Build a small local socket experiment and inspect its traffic.

Learning loop: study → experiment → record evidence → explain in your own words.

Name resolution, request lifecycles, and encrypted connections.

Make it tangible: Annotate a request from DNS lookup through the HTTP response.

Learning loop: study → experiment → record evidence → explain in your own words.

Network namespaces, routing, firewall concepts, and packet capture.

Make it tangible: Connect isolated lab endpoints and diagnose a blocked connection.

Learning loop: study → experiment → record evidence → explain in your own words.

Deployment basics, reverse proxies, configuration, and least privilege.

Make it tangible: Run a local service and document its dependencies and failure modes.

Learning loop: study → experiment → record evidence → explain in your own words.

Metrics, logs, latency, availability, and incident write-ups.

Make it tangible: Measure a small service and write a practice incident review.

Learning loop: study → experiment → record evidence → explain in your own words.

Bring OS and networking observations into one explainable system.

Make it tangible: Publish a lab repository, architecture walkthrough, and learning retrospective.

Learning loop: study → experiment → record evidence → explain in your own words.