You've completed the series

From the kernel to the browser: OS, networking, security, and one HTTPS request traced through all of them. Go back to any step with the series map, or take the Go 120-day plan's capstone, a cloud-edge security proxy that uses every guide at once.

That's the practical lifecycle — from pressing Enter to a rendered, secured, monitored page, and the major mechanisms in between. If you've read straight through, you now have a single coherent model connecting DNS, TCP, TLS, HTTP, global routing, proxies, load balancers, CDNs, rendering, security, traffic engineering, and production operations — pieces that are usually taught as separate, unrelated subjects.

Where to go next, if you want to go deeper on any one piece:

• Networking from Zero (TCP/IP): a slower, hands-on companion for Parts 1–4 here, with home-lab exercises, packet-capture practice, subnetting drills, and 23 Go labs (a DNS client from raw bytes, a pcap decoder, a load balancer with draining, and more).
• The OSI Model, One Click at a Time: the same request seen layer by layer, with a millisecond timeline and a debugging playbook organised by layer. Good for teaching others.
• Operating Systems, Linux, and Containers: Parts 11 and 19 cover Linux's own networking and operations view, and Parts 14–17 cover the containers and Kubernetes your HTTPS services run in.
• Go — The Complete Field Guide and the Go 120-day plan: Part 9's labs grow into the plan's multi-week projects: a TLS reverse proxy, a WAF, API security, DDoS defences, and a cloud-edge security proxy capstone.
• security/real-life-guide.md and security/real-life-security-guide-v1.md: Chapter 12 here is a survey; those guides go deep on threat modeling, PKI operations, and exploitation the way a security engineer needs.
• scale-perf/real-life-scale-guide.md: if Chapters 9, 10, 17, and 21 made you want to load-test one of these systems, this is the hands-on, tool-by-tool guide for that.