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.


That I have a wetware problem.
When I’m debugging, I usually forget the nature of a bug when it is fixed. The more trivial it is, the quicker I seem to forget.
Something does trickle down to my unconscious because I would recognise getting the same error message over and over and that doesn’t seem to happen often, but I could not tell you a single bug in the last thing I wrote, even though I know there were plenty of them.
What really makes this weird is that I sometimes become very upset - we’re talking wailing and gnashing of teeth here - when I can’t find a bug, and you’d think I’d remember those, yet once I do finally track it down and get over feeling angry and stupid, the nature of the bug still disappears from conscious memory.
Now, maybe I am learning lessons because of the infrequent recurrence of the same mistakes, but I’d like to be able to think about them later, and I can’t do that.