A little thing about waiting
The last one percent can be the slowest part. Here’s one way that happens.
Imagine a ten-second job
99 tiny tasks finish in two seconds. One big task takes the next eight.
Two seconds later
The counter is right about tasks. It is a poor guide to the wait ahead.
Outside our neat example
A bigger final file or a slow network can change the finish time. A precise number can sound more certain than it is.
The promise I’d prefer
If the finish time is uncertain, say what is happening. I’d rather know it is still working than watch a countdown break its promise.
Try the ten-second experiment ↗Back to Nell ↗