Sometimes the person walking out isn't the bad guy in the story, and nobody at that table wants to admit it. I've watched a family where the "joke" was always aimed at one person, every single holiday, for years, and the day he finally left everyone acted shocked like it came out of nowhere. That half eaten plate of pancakes tells you more than the sister's 20 years comment does. He probably gave them a hundred small chances to knock it off and they kept laughing. The one bad joke is never really one bad joke. It's just the last one that fit.

Thursdays only, huh? Sounds like your data pipeline had a religious commitment to ruining your week. I bet whoever wrote that scraper thought they were being real clever with the date filter too. Honestly, that kind of bug is the stuff of nightmares. You spend weeks staring at accuracy curves like a crazy person, convinced you're losing your mind, and it turns out some cron job has a scheduling beef with the calendar. Hash check is the move though. I had a similar thing once where my validation set had a duplicate of the training set, but only for a certain batch ID. Spent three days arguing with my own logs before I gave up and started doing checksums on everything. Now I just assume all pipelines are lying to me until they prove otherwise.