Neal Wilson ✅ @neal@social.typica.us

The cat is demanding hugs.

Was planning to have a meal with rice tonight but then I remembered that I forgot to buy rice and am out of that so I'll have to adapt the plan.

The cat has chosen a somewhat precarious cuddle spot.

Today someone tried to order a box of coffee (holds about 12 eight ounce cups of brewed coffee) but staff found that confusing because the words he came up to describe what he wanted was "a six pack". They figured it out eventually.

One of my suppliers has a new article on the tariff situation wrt coffee. Glad to see that it largely lines up with my own analysis (needed to have one because customers are asking), but this is from someone who actually pays the tariff. https://royalcoffee.com/understanding-the-impact-of-new-tariffs-on-coffee-imports/

In related news, the automations I've been setting up for Mac builds have been replicated for doing Windows builds. Feels kind of janky to be relying on WSL for that but after a bit of config work and Powershell scripting it's working so I'll take the win.

*Me doing Windows related sys-admining* "Oh, that's kind of neat... I have no idea what I'm doing... WTF is up with that default?"

The cat is demanding hugs

Alternately, you could just slash that to 0 and get better outcomes.

The new decaf French Roast is now the most expensive coffee for me to produce (the next decaf Sumatra might be a little more depending on how I decide to roast that, it'll be close regardless). In a normal year it would be in the lower quarter of the product line. This is based on a shipment not affected by tariffs so who knows where that's going to end up.

The new decaf Brazil turned out excellent. Very happy with the quality there.

Tasting production test batches of new coffees. So far things are matching expectations. I'll have some blends to rework over the next few days, but I'm not anticipating difficulties with that.

There are also some problematic features that in a practical sense I'm dropping for the 2.0 release. Not because they're bad ideas, but because I need a better way for people to work with it. I'm leaving in as much as I can to support whatever the replacement looks like so I can hopefully bring that back in early in the 2.x cycle.

Doing releases in the 1.x series was always kind of a pain since I'd always do primary development on one platform and there's inevitably something that's not quite right on the others that needs to get fixed up at the last minute. I'm hoping that I can have a better workflow with more testing on all platforms as I go in the 2.x series.

Last night I set it up so that it's much more convenient for me to do Mac builds of Typica and make sure things are working there. I plan to do the same sort of change for Windows builds. Maybe some day I'll have that fully automated.

Multitasking cat petting, shell scripting, and trying to find a Maelific on floor 10 in Wizardry so I can get the platinum trophy.

Today I got to see the next door neighbor's good dog being silly.

(I don't actually see this as a problem. Sometimes having the stopwatch value persistently there is useful, other times it's not, and the control to switch from one behavior to the other is conveniently accessible.)

KDE Connect is apparently picking up a fresh notification every second if I run the stock stopwatch on my phone. This makes it impossible to dismiss the little notification thingy unless I switch to Do Not Disturb mode.

I have, at least, locked in my price on what I hope to be my next year of Costa Rican coffee and am not expecting a need to raise prices on that one any time soon. Historically that's been on the more expensive side of my line, but that might not be true anymore by the end of the year (and not because it's getting cheaper).