Topics / web
Web and networking
Everything between a URL and a pixel: the protocols that carry bytes across the internet and keep them private and fresh, and the browser machinery that turns them into a page.
- DNS, before there is an address, 10 levels · 43 min · Idea to Machine
- HTTPS, before the first GET, 11 levels · 42 min · Idea to Silicon
- A passkey, from the button to the chip, 9 levels · 36 min · Idea to Silicon
- HTTP/3 and QUIC, from request to datagram, 10 levels · 45 min · Idea to Machine
- HTTP caching, down to the disk, 9 levels · 38 min · Idea to System
- CORS, at the browser’s boundary, 8 levels · 38 min · Idea to Machine
- WebSockets, down to the frame, 8 levels · 40 min · Idea to Machine
- WebRTC, from Join call to the wire, 10 levels · 50 min · Idea to Machine
- Video streaming, down to the decoder, 9 levels · 38 min · Idea to Silicon
- How a push reaches your lock screen, 10 levels · 43 min · Idea to Silicon
- How HTML becomes pixels, 9 levels · 42 min · Idea to Silicon
- WebAssembly, top to bottom, 10 levels · 40 min · Idea to Machine
The path
Read in this order and each dive leans on the ones before it. Every dive also stands on its own.
- 01
DNS, before there is an address
Your laptop knows a name. The network needs an address. Follow a café Wi-Fi lookup through delegation, caches, signed answers and encrypted transports, down to every byte on the link.
Idea to Machine43 min10 levels
- 02
HTTPS, before the first GET
One round trip to agree on keys, prove a server’s identity and hide an HTTP request. Follow TLS 1.3 from the first visible byte to the silicon doing the encryption.
Idea to Silicon42 min11 levels
- 03
A passkey, from the button to the chip
Ana signs in without sharing a secret. Follow her passkey from a phone to a laptop, through the browser’s origin checks, a real signature, the USB frames and the hardware boundary that protects the key.
Idea to Silicon36 min9 levels
- 04
HTTP/3 and QUIC, from request to datagram
How HTTP moved off TCP: head-of-line blocking, QUIC streams and packets, a TLS 1.3 handshake folded into the transport, and the UDP datagrams carrying it all.
Idea to Machine45 min10 levels
- 05
HTTP caching, down to the disk
Open a news article twice. Follow its HTML, JavaScript, logo and comments through freshness checks, validators, service workers and the back/forward cache to see which requests ever reach a server.
Idea to System38 min9 levels
- 06
CORS, at the browser’s boundary
Your app can reach the API. Why can’t it read the reply? Follow one JSON order through origins, preflights, cookies and the browser’s response filter, down to HTTP/2 frames.
Idea to Machine38 min8 levels
- 07
WebSockets, down to the frame
Why the web needed a full-duplex pipe, how an HTTP request turns into one, and what every bit of a WebSocket frame means on top of a TCP stream.
Idea to Machine40 min8 levels
- 08
WebRTC, from Join call to the wire
Ana is behind her home router. Ben is behind a carrier NAT. Follow their video call through negotiation, hole punching, encryption and the packets that arrive just in time.
Idea to Machine50 min10 levels
- 09
Video streaming, down to the decoder
Press play on a ten-minute talk. Follow the first picture, the next segment and a sudden tunnel through HLS, DASH, adaptive bitrate, browser buffers and the silicon that turns bytes into motion.
Idea to Silicon38 min9 levels
- 10
How a push reaches your lock screen
Your chat tab is closed. Ana is running five minutes late. Follow one encrypted message through keys, queues, a sleeping phone and the bytes that wake it.
Idea to Silicon43 min10 levels
- 11
How HTML becomes pixels
One product card, from arriving bytes to a glowing display. Build its DOM, resolve its CSS, and find out why moving a badge can cost a frame.
Idea to Silicon42 min9 levels
- 12
WebAssembly, top to bottom
Start with real C zlib compressing your text in this tab. Then go down through the JavaScript boundary, the module format and the stack machine to the guard pages and x86-64 an engine uses to run it fast and safely.
Idea to Machine40 min10 levels
Notes
Practical answers in web and networking.
Find what makes a page interaction slow
Use Event Timing to separate input delay, handler work and presentation delay, then correlate slow interactions with long animation frames and a DevTools trace.
Set up passkeys: the minimum server checks
Generate fresh challenges, bind them to the ceremony, and verify origin, RP ID, flags and signatures before creating a session or storing a credential.
Send a Web Push notification from Node
Generate a VAPID identity, save a browser subscription, and build an encrypted push request with Node crypto before sending it to the subscription endpoint.
Cache-Control recipes that actually work
Choose response directives by whether data is public, how long staleness is acceptable, and whether a stored response may be reused without validation.
SSE vs WebSockets vs long polling
Use SSE for server-to-page text updates, WebSockets for bidirectional streams, and long polling when ordinary request handling is the simplest fit.
Check whether a site uses HTTP/3
Check client support, inspect HTTP/3 advertisements, then confirm the actual connection protocol with curl or browser DevTools.
Read a TLS handshake from the command line
Use OpenSSL to check the certificate chain, hostname and negotiated parameters; use curl to see the HTTP request on the same connection.
Debug DNS with dig
Compare recursive and authoritative answers, inspect status and TTLs, and distinguish DNSSEC signals from local validation.
Put card buttons beside links, not inside them
Give navigation and actions separate HTML controls. A sibling link and button work with the mouse, keyboard and assistive technology without event-cancellation patches.
CORS: a practical response-header checklist
Diagnose a blocked browser fetch by checking the origin, preflight response and credential policy. CORS controls what scripts can read; it does not authenticate a request.
Other topics
Languages and runtimes
The work a language runtime does on your behalf: scheduling goroutines, collecting garbage, and running portable bytecode safely and fast.
6 dives · 5 notes · 4.5 h of reading
AI models
How neural networks learn from data and get shaped into assistants, and the architectures that turn text, images and sound into predictions.
6 dives · 1 note · 4.1 h of reading
AI serving
What it takes to run a model once it is trained: generating tokens fast, fitting weights into memory, coping with long prompts, and connecting models to data and tools.
6 dives · 8 notes · 4.8 h of reading
Systems and hardware
The machine under all the software: how a processor executes instructions, what memory really is, and how a GPU keeps thousands of threads busy.
6 dives · 4 notes · 4.6 h of reading
Infrastructure and operations
Deploying and operating software: Kubernetes workloads, Helm releases, Ansible automation, Raspberry Pi clusters and the practical checks that keep systems running.
6 notes · 0.3 h of reading
Application development
Building applications and data workflows: framework patterns, Django and Wagtail models, Next.js integration, identity schemas and practical data scripts.
5 notes · 0.2 h of reading