Frontend Labs
⋯

What you will be able to do at the end

  1. Explain what happens, step by step, between pressing Enter on a URL and seeing a page — with no hand-waving.
  2. Read an IP address and subnet mask and say exactly which addresses are on that network. (Subnetting stops being scary.)
  3. Use ping, traceroute, dig, curl, ss, and tcpdump deliberately rather than hopefully.
  4. Look at a packet capture and describe what the two machines are saying to each other.
  5. Diagnose the five most common network problems by their fingerprints, instead of guessing.
  6. Explain TCP's handshake, reliability, flow control, and congestion control — and why a connection is slow.
  7. Build a small production-like lab with DNS, TLS, load balancing, firewall rules, containers/Kubernetes-style networking, monitoring, and packet captures.
  8. Write your own network tools in Go: a DNS client, a pcap decoder, a TLS inspector, a load balancer with draining, a blackbox prober, and more (§0.8 lists all 23 labs).
  9. Know what to read/watch next.

Generated from real-life-guide-v1.md · 8 Oct 2026 16:36