A while back I was developing a workflow scheduler. However the run duration kept coming back negative. The runs kept finishing like 15 seconds before they started. Eventually I figured out why; the company had configured a policy to use their custom NTP server, but it was 16.7 seconds off. So my Windows laptop’s time was in the future, but the WSL VM (which ran the program) used another NTP server and was correct. In the end I just added a bodge that made the program request the time from an external server on startup to calculate an offset.


i was just a user, but i debugged a weird issue where one of those blue light reduction programs would start flickering and inverting day and night time during june.
turns out the dev had made the assumption that the sun always rises before it sets, and i was far enough north that the sun would start setting after midnight.
https://zainrizvi.io/blog/falsehoods-programmers-believe-about-time-zones/
https://youtu.be/-5wpm-gesOY
Watching this makes me want to dump all timezones, and daylight savings in the wood chipper.
Everyone should set their clocks to UTC.
Such a classic.
haha, knew what this was going to be. Already came close to posting it a couple of other times in this thread. :)
Ooh, interesting one! 😄