Neal Wilson ✅ @neal@social.typica.us

Use case #2: You're doing an experiment where you want to vary a part of the roast in the middle, while keeping the start and end the same. Having a later translation point makes it easier to match the end without having to design the whole modified plan up front. (which you should, but we all know coffee roasters aren't great at actually doing things like that in the real world for the most part)

Use case #1: You're far enough off the plan at the start of the roast, think you're running parallel, but want an early translation to make sure you're on the right track before the auto-translation at the start of taste-able chemistry kicks in, making it easier to match the significant parts of the plan.

Added a new feature to Typica that I've wanted for a long time now: Immediate Translation. This lets you shift live data or plan data across the time axis to make it look like the temperature of the coffee is ascending through its current value at the same time in both without needing to specify a fixed point in advance. You're just saying, "line it up now". This augments the previous behavior rather than replacing it.

Tonight the cat wants belly rubs.

Tonight's potato was better.

I'm eating a baked potato. It's not the best baked potato I've ever eaten, but it is at least edible. It's been a while since I had one.

I had 4 feature changes that I wanted to make before roasting the coffee today. All of them pretty minor, all implemented without difficulty. The one I expected to be the most difficult was something that I had already mostly implemented as part of earlier feature work and I just needed to hook it up the right way.

Current state of the cat

The cat has decided that scritches are no longer enough. She must sit on me.

The cat is in the mood for scritches tonight.

Took another look at a piece of code I wasn't happy with and proved that half of the conditionals were redundant. Took those out, which let me sensibly remove a temporary variable and did a couple other minor tweaks and now I have something that's shorter (both width and height), earlier to understand, runs faster (though that won't be noticed by anybody), and has exactly the same behavior.

Pyrotechnics are disturbing the cat. Maybe I'll have peanut butter on crackers while assuring her that everything is fine.

Removed Sulawesi Toraja from the the shop's web site. I still have a little of that available to sell locally, but I can't roast any more until I have more green coffee available. Online orders from now won't go anywhere until after the 4th, but I'll roast for any orders that come in on the 5th and try to get all of that shipped promptly.

https://wilsonscoffee.com/

Having now looked into it, pretty sure the problem is two conditionals that are the wrong way around such that the whole thing always evaluates as true even if it shouldn't.

Fixed, observed behavior is correct, but there's still a conditional that's not quite right causing a thing that should only have happened once to instead happen 5 times, but with 4 of them correctly being effective no-ops. I'll have to look into that a little later.

Trying to track down a minor bug: a function that I was expecting to be called 5 times was in fact called 1,693 times. So that's something to investigate.

Credit union tried to put my money in the wrong account. I caught the error right away and they fixed it, but now I know the name of someone with an account number that's the same as mine except two of the first three digits are transposed, so that's a bit of a privacy fail despite an apparent effort at not disclosing that sort of thing (the first half of the account number is redacted on the receipt, but it's a short enough number as to not leave many possibilities).

I don't know how I ended up on the alumni email list for a particular university. I never enrolled there, never took a class there. I did a guest lecture there once.

The cat strongly recommends petting the cat.