From the perspective of my staff actually using the thing, the main downside is that the hot water dispenser is locked for the part of the brew cycle where no additional water will be used. I could set the drip delay to a minimum value to work around that, but that would unlock the brew baskets early and not have a realistic count down to when they can actually use the coffee that's brewing so I'd rather not make that change. Aside from that the new one is easier for staff to use.

Show thread

New brewer has some nice changes and some not so nice changes. Programming the thing is worse as the touch sliders don't have step change controls (at least not discoverable ones) so I need a compatible stylus (which I could thankfully find) to get the values set precisely where I want them. On the plus side, there's bypass which I'm not currently using but have sometimes wished that the old one had it and if we need to we could move from 3L airpots to 1 gallon now.

A test batch of decaf with the regular settings I came up with resulted in something that tastes the same as what staff brewed by hand just before the new machine got installed so it looks like I don't have to do anything there yet. It'll be a thing to keep an eye on, though, as it's not uncommon for me to need different settings for decafs. At some point I'll also want to bring in the refractometer to double check strength.

Show thread

Regular coffee out of the new brewer is now delicious. I did need to make some programming changes as the default settings weren't great for my coffee. Next is seeing if I still need a separate setting for decafs.

Show thread

The main cause for concern with the new brewer was that the wiring diagram in the manual does not match the physical reality of the machine (the diagram sticker on the inside of the machine is a little better and cross checking that against the older brewer had me reasonably confident that I was doing the right thing wiring that up), but the water inlet isn't leaking, the one solenoid I've checked is working, and it's heating up so I think I've done it right.

Show thread

Today was supposed to be a stay home and write software day, but the freight truck with the new coffee brewer arrived faster than expected so I'm getting that set up instead so we can stop brewing all the coffee by hand.

An already bad looking week now looks rather worse. Was called in several hours early because apparently the coffee brewer's boiler developed a leak overnight. This is something that is in theory repairable, but the part+repair costs close enough to a whole new brewer so until that arrives and gets installed we're brewing by hand.

Got a little more work on Typica finished tonight. Small feature improvement and small code size reduction (and fewer lines needed in code I know I still need to write later). The upcoming week doesn't look good for further progress on that but I've got a list of small things that I can try to deal with.

Today's spam is particularly tone deaf. I do not believe for 1 second that 2 different people have written a near identical pitch for a new web site design and think they're going to make a several thousand dollar sale on a 2 decade old free software project that has never finished a year fiscally in the black. (Not that the details of the emails even make sense as something that might be even remotely desirable if I had the budget for that.)

Working on porting over another report today. As I go through these I'm taking the opportunity to rethink the SQL and speed things up where I can.

(I don't think Zapfino should be the default serif font [but only when bold])

Show thread

Added limited customizable styling to reports in Typica. This is mainly because it's apparently possible for the font substitution algorithm to go very wrong. I probably need to add more customization options later, but now there's a place for all of that sort of thing.

Phishing scam: "We couldn't renew your Claude Pro subscription."

Me: *Never had one to renew in the first place.*

Ported over a Typica 1.x feature into the 2.x code base and made good progress on a completely new feature. Probably won't be able to get the new feature finished up tonight after dinner but I don't see it not being ready for the 2.0alpha2 release some time before the end of the month.

Car repairs were faster than expected. Had I known they'd get to it as fast as they did I would have just waited for it there (trunk latch stopped latching so I've been driving around with some primary wire [it was what I had to work with when the problem started] tied inside so that it at least looked close enough to closed that other drivers wouldn't honk at me).

Two dreams last night featured a new character: a giant talking bee (approximately 5x normal bee size). I ate it part way through the first dream but it was back for the 2nd.

I seem to do this about once every 3-5 years (modifying someone else's Python, generally having no idea what I'm doing, but making it work in the end).

Show thread

Needed a tool, didn't want to write it myself, found something that's almost what I needed, modified the Python to add the missing feature in a hacky works for me but would be totally inappropriate to upstream way.

I don't know Python but I can read the code, search for documentation, make reasonable guesses, see what the error messages say, &c.

Nobody realises that cats have been hacking Alpine systems by just walking long enough on the keyboard.

Just saw a picture taken in my shop in the NPR app. The story wasn't about coffee (a politician who won in the election had done a couple things here and an AP photographer was out for one of them).

Show older
Typica Social

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!