|
|
|
|
|
by kazinator
1389 days ago
|
|
The counting activity doesn't begin when the first item is registered; it begins when the counter is initialized to zero. A decision is made to begin counting, along with the realization that nothing has been counting yet. That's when counting has started. When the first item is seen, the counting is then continuing. Suppose your job is to count some events. You check in for work at 8:00 a.m., but the first event has not registered until noon. By your logic you should not be paid for four hours, because you're paid to count, and counting started at 1. |
|
We are talking about the he numbering, not the work-doing.
You start waiting at 8, and you wait between events. But you only count (increment) when an event happens.
The 0 comes for free when you are ready to count (hello golang and C++, as well as human intuition).
When you count stars in the sky you don't say "0, 1, 2".
You say "..., 1, 2", or if no stars show up, you say "there are 0" after timer expires.