[captaincrowbar]

Some people, when they have a problem, think, “I know, I’ll use floating point.” Now they have 1.9999998 problems.

[beezle]

Funny story from today while briefly on hold for a support rep. Got the standard 'we'll call you back if you want blah blah' followed by - I kid not - "you're estimated wait time for the next representative is 0.58333333 minutes"

At the end of the call I suggested if she can log a problem for IT to include this and that they should either round up or use seconds (I suspect it was 35 seconds)

[__s]

We had this issue with time estimates at work. JIRA field was minutes, which got printed as fractional hours elsewhere. Not good if you put 20 minutes. So suggestion was to use 15 minute intervals, but I pointed out that as long as you used multiples of 3 you'd get 2 digit results, so I'd round to multiples of 3 instead

[eru]

Those are ridiculously fine grained tasks (or very precise estimations)?

Anything that takes less than an eg half an hour, I would probably just do, instead of making a ticket and an estimation. But I guess some companies are more bureaucratic than others?

[recursive]

Some numbers can be precisely represented using IEEE-754 floats. Two (2) is one of them.

[eru]

Yes, but not every calculation that yields 2, also yields 2 when performed in IEEE-754 floats.

[recursive]

Yes, but any calculation that you'd use to count whole units things, like reasons, that would result in 2 would yield precisely 2.

[eru]

Yes. The quip was only a silly joke.

[markab21]

I bet you have been waiting years to pull that one out of your pocket.

Well played sir! Nice shot man! :D