News for hackers. Stuff that matters.
Re:FloatCompMandelbrot: What impact does floating point prec... by beezle on Tuesday March 12, 2024 @08:59PM (#39686847)
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)

Re:FloatCompMandelbrot: What impact does floating point prec... by __s on Wednesday March 13, 2024 @07:01AM (#39690038)
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
Re:FloatCompMandelbrot: What impact does floating point prec... by eru on Friday March 15, 2024 @04:31AM (#39713337)
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?