Now that I've kludged around all the new issues I've been looking at and taken a good look to see which changes I could remove, I'm left with the conclusion that not my code just changed in a way that my code was not compatible with and there are things that just need to be inexplicably different to get the right behavior. I hate that conclusion, but I think I've ruled out the other possibilities.
Got an email asking me to "share my experience as a postdoctoral researcher" and while I have contributed to a number of scientific endeavors, I'm no where close to have even gotten a doctorate (I've been getting good job offers since I was like 12, my experience with formal education was not great, and I decided not to take on soul crushing student debt).
The problem with what I did seems obvious in hindsight and there's a pretty straightforward fix, but I need to be working on other areas today.
A bit of code I wrote recently in an attempt to make a program not use 100% of a CPU core ended up slowing down data propagation in such a way that everything looks like it works until you try to use it for real, at which point it quickly becomes apparent that it's become useless. I have a few ideas for how to really fix it, but for now I'll take useful operation at higher than needed CPU utilization over honestly still higher utilization than I'd like but not being useful.
Pulled out some old training material KSAs because one of my employees is getting school credit for the job (may as well if you're doing the job anyway) but one of the things I'm supposed to sign off on is so far outside sanity (crap rich people like that nobody else cares about) that I've made the allowable substitution coffee and barista skills, pulling key points from a recognized certification in the industry (I helped define those cert requirements, I may as well reuse the resources)
Did a big pile of refactoring in preparation for the next chunk of new functionality I want to add. I'm going to need to rewrite all of that again later, but I don't have the time right now to jump straight to what the implementation is going to be at release as that's a lot of additional work mostly unrelated to my current train of thought and I'd rather get the thing I'm working on up and running so I can make sure that's working properly while the relevant details are still in my head.
Author of Typica software for coffee roasters.