I’d never really thought of time estimation as working best when you start with the final answer and work backwards to estimate what you can do within that time period, but that really does make a lot of sense. I think I have often done this without consciously thinking of it this way.

I mean, that’s just basic cooking technique!

Nah, just cook them very, very, very thoroughly first, and you’ll be fine.

The whole reason why an entire instruction was added to ARM to facilitate conversion to integers is because people need integer semantics from their numbers and so the language has to support this efficiently. Thus, in practice there already two number types, it’s just that they have been merged together in this incredibly messy way so that you have the worst of both worlds.

It is the 0-th element after the start of the array. 0-based indexing is very common in both mathematics and computer science.

What does it mean to access the element at index π of an array?

There are tons of languages that let you represent integers directly as integers rather than having everything be a float so that you do not have to worry about this problem at all.

If only we had built the web on top of a language that did not have such insane handling of its numbers in the first place…