I'm almost certain I know what the problem really is now, but I'd like to see the full details of the failure before working out what the fix needs to be.
Lately I've been trying to track down a calculation problem in one of my programs. It's the obnoxious sort that sometimes happens a lot and sometimes runs for hours without issue. I've at least gotten as far as identifying what I think is the first place in the code the issue can be detected, but after putting in more extensive debug output to capture erroneous state without interfering with live use, the problem stopped again. I'll keep checking back with it over the next couple days.
I'm going to try to replicate the first and last cups from the middle row. The lighter one is excellent on its own while the darker is potentially more versatile in blends.
My last coffee delivery for the year arrived while I was out running errands. I hadn't gotten the PRO# to track this and see that it was getting delivered today, otherwise I would have waited for it, but staff handled it perfectly without me so I'll be able to get on with product development right away.
My mother wanted a microwave for Christmas this year so we got that sorted out today. My favorite feature of her new device is that if you don't set the clock (she already has 2 clocks in the room that she's not using) it doesn't show anything on the display. No flashing 12:00, no lights (and certainly no blinking lights).
Personally, I will always prefer a thoughtfully created purpose built interface for anything work related even if only for the massive feature discoverability benefits (rather than asking if the system can do something and then get a lie in reply).
Author of Typica software for coffee roasters.