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.

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 11 hours ago* (last edited 11 hours ago)

Back when I was learning c++ on Windows, I naively jumped right into game dev (as one does) before understanding the purpose of a debugger. I spent 3 months chasing down a period that should have been a comma. Due to function overloading, this was not an error or warning. It's just silently calling the wrong function and crashing the program.

Thus began my distrust of magic compiler features. To save typing a handful of characters, languages add new ways to blow off your own leg. Every time you blow off your leg, the time you lose is orders of magnitude greater than just being explicit. Just read this thread for more examples. Today, I program almost exclusively in C. I have no desire to use more feature-rich/higher level languages for anything.

  • source