Neal Wilson ✅ @neal@social.typica.us

The feature is mainly to catch data entry errors and should be set conservatively based on whatever the actual machine is, but if you don't care about that the defaults won't get in the way for almost everybody. There is a limit to how high you can set the limit, but it's about 4x global production (even more if you set the unit to Kg) which I don't anticipate anybody coming anywhere close to doing. Limits can be expressed in Lb/Kg/g depending on what makes sense for the user/machine.

I've been fleshing out the settings editor for the next version of Typica lately and have made a change to how that handles batch size limits. That was originally introduced as an optional feature with the default to not limit things at all. Going forward that feature is always enabled, but the default limits are 0 (because negative batch sizes are not possible in this universe) and 1000 pounds (anybody trying to use this with a 7 bag or larger roaster may need to change the setting).

Production test batch on the new coffee from Sulawesi turned out delicious. I'm still roasting this quite dark (it's not anywhere near as interesting on lighter roasts). Good body, kind of smoky, but also ever so slightly sweeter than the previous lot. I don't anticipate difficulty adapting the blends that's used in.

Be cat; do nap.

Sorting out the new Sulawesi from the latest coffee shipment today. There's one more coffee to run out of the previous lot and figure out the new one, but it looks like that should happen before my next trip so staff should be able to just focus on normal production.

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.