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’ve told this story before but we were supporting a custom ATS for a customer where we had this perfect storm happen.
Searching... 10 applicants found debug_pageorApplicant: Mohammad Al-Saud send_to_processing.So we got an email from the customer saying they had a VERY offended job applicant and what had happened. They had clicked the reject button on someone, which triggered the system to send an automatic rejection form letter to the applicant. This applicant had some Arabic character in their last name, which triggered the bug.
And the reject applicant function had been written by this guy. So that poor applicant got an email that said
Dear Applicant
We have reviewed your application and while we thought you have an excellent background unfortunately we decided you are not a good fit for our company at this time… blah blah blah etc…
YouCanHazNoJobKThanksBai