@@PairingWithDuncan Maybe. Does that suggest that it can't read the computer's clock, or that the developer who created the tool doesn't know how to tell it how to read the clock. Maybe my developer's code's developer was incompetent...
Maybe Intellij is reporting CPU time instead of clock time. I/O would report less CPU time than clocktime, for multithreaded calculations it would be the opposite.
That's great! My developer lies to me, and my developers tools lie to them.
Looking up the definition, a lie is a knowing untruth. I do wonder if the tool is deliberately or accidentally deceiving
@@PairingWithDuncan Maybe. Does that suggest that it can't read the computer's clock, or that the developer who created the tool doesn't know how to tell it how to read the clock. Maybe my developer's code's developer was incompetent...
Like your investigation on test execution duration! Since most of developers don‘t care 😊
I think that’s true, but it’s a shame, because the tight inner loop can feel really nice and productive.
'Enter' to complete the current word.
Ooh, that would be simple, thank you. I’ll try to remember that when I’m next in the situation
Maybe Intellij is reporting CPU time instead of clock time. I/O would report less CPU time than clocktime, for multithreaded calculations it would be the opposite.