who uses microsecond-based timestamps anyway
you don't need to track time that closely. it's vain to do so
0 Boosts
0 Likes
this is being used to track database entry expiry.
for a process that runs /daily/
a DATE would have been fine here, seconds would have been overkill, milliseconds would have been extravagant, MICROSECONDS is just going way, way too far
nanoseconds would just be taking the piss
ugh. my least favorite part of modern type-checked python is when the typechecker disagrees with reality.
like I try to commit my code and the pre-commit hook runs the typechecker and yells at me:
error[unresolved-attribute]: Object of type `Logger` has no attribute `debug`
and I'm like... yes it does have that attribute. I have run the code, it has called logger.debug() many times, which it wouldn't be able to do if there was no debug().
So you're wrong. But WHY are you wrong?
my experience programming is not improved by having a checker that is wrong about if my code is correct
TAI64N, baby!
@cazabon that's even worse
@foone My Stratum 1 GPS-backed NTP server has a margin of error of +/- ~65 ns. In antiquity, I would be worshipped as a god. But no, it's just a computer the size of a pack of playing cards, wearing a funny hat.