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.

    • CookieOfFortune@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      42 minutes ago

      Back in the day not saving means you might lose your work during a crash. So ctrl-s after every change became habit even years into auto saving editors.

    • Buddahriffic@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      8 hours ago

      Or variations of this caused by a makefile not having correct dependencies set up, eg it points to dependent source files but not the headers so header updates get ignored during compiles. Made me add a “make clean” step to the debug process of “change that should have fixed the issue appears to be doing nothing at all” issues, or even just defaulting to rebuilding everything because test times can take hours or even days to get to the issue, so I don’t want to waste that much time only to find out it’s still running the old version.

    • bss03@infosec.pub
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 hours ago

      Yep. Last time I used MS Visual Studio it was still all too eager to run an older binary, and I lot plenty of time debugging a binary that doesn’t reflect the current code. And, even more recently, when testing requires you to remember to run separate routines to upload to a testing server and restart a service, it is really easy to forget to do that when you are bouncing between the code and the browser console to figure out what to change.