Waiting is uncomfortable in a specific way: it removes the ability to act without removing the urge to. That gap is where most of the damage on this list happens. Almost nothing here is exotic. It is the ordinary set of things people do when a screen stops changing.
The individual cards say what is safe and what is costly for their particular wait. This page collects the parts that apply everywhere.
Safe during any wait
- Write down where you areWhat you pressed, what you saw, and roughly when relative to everything else. Not for anybody else. For you, in twenty minutes, when you have forgotten whether you already pressed it.
- Decide the condition that ends the waitNot a time. A condition. Something you can check and get a yes or no from. Deciding it now, while you are calm, is much better than deciding it later, while you are not.
- Read the card for the wait you are inMostly so you can find out whether the silence you are looking at is the expected shape.
- Do the work the wait leaves room forSome waits come with real work attached. Recovery material that appears once is the clearest case, and it is free to handle properly while you are stuck anyway.
- Leave the tab aloneNot closed. Alone. A tab you are not touching is a tab that is not sending a second copy of anything.
The things that quietly restart the clock
These are the ones worth learning, because none of them feels destructive at the time. Every one of them is an ordinary reaction to a screen that is not moving.
- Pressing a submit button a second time. On a page view this is harmless. On anything that writes, it is the most expensive thing in this list, and it is covered on the order going through.
- Reloading during a write. A reload during a read costs you a round trip. A reload during a write costs you a state you cannot see and cannot undo.
- Asking for a new path because the current one feels slow. You are trading a known path for an unknown one, and the sample you get back is not better for having been requested angrily. See building another circuit.
- Retrying something that is throttling you. Several waits get longer each time you touch them. A cooldown is the obvious case, and it is not always signposted as one.
- Writing a second message before the first has been read. It does not raise your priority. It usually lowers it, and it makes the thread harder for the person to answer in one pass.
- Going looking for a replacement address the moment one stops answering. This is the single riskiest reaction on the whole site, and it is why an address coming back exists as a card.
- Filing a ticket about a wait that has not finished being a wait. It joins a queue and it commits you to a version of events written while you still had the least information.
The rule that makes all of this easier
Set the condition before you start, not during. Before you spend anything, before you send anything, before you press anything that writes, decide what you will do if it does not resolve. It takes a moment and it removes the decision from the worst possible moment to be making it.
This is the whole content of the pause you add yourself, which is the only wait on this site that you choose, costs nothing, and is worth more than any of the others.
Why the urge to act is so strong here
Ordinary software gives you feedback. A spinner moves, a bar fills, a count goes down. Almost none of that survives on a network where every extra request costs a round trip, so the screens in front of you are unusually silent by design rather than by neglect.
Silence reads as failure. That is not a character flaw, it is what people are trained to expect by everything else they use. The result is that a completely healthy wait feels indistinguishable from a broken one, and the only difference is knowledge you have to bring with you.
That is the entire reason this site sorts by duration rather than by subject. If you know the mechanism underneath, the silence stops being ambiguous, and once it stops being ambiguous the urge to press something goes away on its own.
A short version to keep
- Name the wait. Which of the thirty six is this, and if none of them, which of the five bands does the mechanism put it in.
- Do not touch the thing you are waiting for. Not a reload, not a second press, not a new path.
- Ask whether a clock is running elsewhere. If there is a deadline in the picture, that is your only urgent item.
- Set the condition that ends the wait, and write it down so the version of you in an hour does not renegotiate it.
- Leave. Almost every wait past the shortest band resolves better without an audience.
When doing nothing is the wrong answer
Patience is not always the right posture. In the days band there is often a countdown running underneath the wait, and the deadline belongs to you rather than to the thing you are waiting for. Waiting politely through a countdown is how people lose the ability to act at all.
So the rule is narrower than it sounds. Do nothing to the thing you are waiting for. Do check whether a clock is running somewhere else. Those are different activities and the cards in the days band spend most of their length separating them.
What this card is not. This page is not advice about anything outside a screen, and it does not cover what to do about goods, people or money beyond the mechanics of the wait itself.