Just sent a transfer, and being stuck in the mempool waiting feels a lot like rush hour on the subway: you clearly got on the train, but there are too many people in front of you, and the turnstile just won't let you through. Basically, it's a bunch of transactions waiting for miners to pick, and if you pay a normal fee, you'll slowly queue up; during congestion, you might even get bumped off or replaced, and all you can do is stare at the confirmation count in a daze.

What's more annoying is that some on-chain data tools/tags show "delivered," but that's just their own perspective; if there's a slight delay or a misleading signal, it's easy to misjudge: is your transaction not sent out, or has it been sent but not included in a block yet.

I now tend to think of "redundancy" as a backup analogy: preparing two sets of measures for the same thing—separate addresses, separate devices, and separate confirmation paths. It's more trouble, but at least it helps keep a stable mindset during congestion.