Keep names and addresses separate
A name is a durable label. An address is one answer about where to try a connection. Treating them as separate observations makes a problem easier to describe.
The complete index
Notes
Seven self-contained readings, connected by the habit of keeping a question clear.
Start with a title that matches the question in front of you. Each note has a contents list and links back to the index; the sequence is a suggested route rather than a requirement.
What a verified connection tells you
A certificate check connects a secure session to the requested name. The page returned inside that session still deserves its own review.
Delay and throughput answer different questions
A quick first reply and a fast transfer describe different parts of an experience. A single number cannot stand in for both.
Read a failure one layer at a time
A connection can fail before a name is resolved, during a secure handshake or after a request arrives. Naming the layer narrows the next check.
Compare two attempts fairly
Two numbers become a useful comparison only when their conditions are known. The differences around the numbers can matter more than their size.
Draw the boundary before collecting detail
A clear boundary makes a note smaller and more trustworthy. It tells a reader which conclusion the evidence can support.
Revise a note without losing its context
A living note should become clearer as evidence changes. Preserve the reason for a decision without keeping every intermediate draft in the reader's path.