Why the iPhone Timer app displays a fake time
I&#x27;ve never seen something so confusing. I&#x27;ve been (and quite frankly still am) seriously considering this is a big prank that&#x27;s going over my head. The author even mentions that because time goes up and countdowns go down, rounding down is confusing. Wouldn&#x27;t the logical conclusion be that you needed to round up?<p>Wouldn&#x27;t rounding up be the most logical option ANYWAY? If someone counts me down, I expect them to say &quot;5, 4, 3, 2, 1, GO&quot;, and I expect a timer to do the exact same thing. This fixes seemingly every issue, starting on 5, not having to round to nearest integer (or add 500ms, which is an odd way to look at it, but sure), and not showing 0 (which I&#x27;d find quite weird).
I just checked my own (Android) timer, and sure enough it rounds up, which is what I expected and what I expect from a countdown in general.<p>Maybe what seems to me like the most obvious behaviour for a timer is not as obvious as I think, but why did the author not even mention rounding up as a solution, or how it could conflict with his own expectations?<p>I&#x27;ll just assume this to be a shower thought that didn&#x27;t fully mature before making it into an article, but there seems to be enough effort that I&#x27;m still left quite confused.
Oh and don&#x27;t mistake this for a euphemism for me critiquing the intelligence of the author, at worst it&#x27;s just a funny blindspot (as we all experience) but I&#x27;m seeing very little mentions in the comments here, which only adds to my bafflement.