Neal Wilson ✅ @neal@social.typica.us

The cat helped me log into the computer. I typed my password, she pressed Enter (her favorite key).

Some hardware I ordered back in April estimated to ship last week has apparently been pushed out to a new estimate for the 2nd week of August. I'm not going to bother writing code to hook into that hardware until I have a unit to test that code against.

Had a phone call with the person I'm developing a new class with. We seem to have a good working rapport and this is coming together nicely. It also looks like we'll be filling up both sessions (people want to take our class), so that's nice.

My latest bug fixes work. Also streamlined the process for getting the latest updates over to the computer at the coffee roaster.

Also got approval to upgrade the shop's Nextcloud server which needs more disk space.

Made a big batch of chai concentrate today.

It's a cat.

cat

First batch roasted with the new feature turned up some minor, easy to fix issues. There's also one or two more sub-features that I think might be nice to have that I'll try to put in and see if I really like it in practice.

Current state of the new timer indicator with a long plan loaded. I ran into the character limit describing all the features, but I believe everything shown here now is working rather than just being a design placeholder. The most recent thing I did with this was the range timers on the right which show live and planned durations, the name of the range, and which range(s) is active. There's a fifth range that's not shown, but it's in a flickable/scrollable area so that can be seen.

I have more details about what I'm teaching at CRG Retreat. It looks like they want a new class and I'll be teaching one session while a first time lead instructor will be teaching the other and we'll station instruct for each other. My thinking is that I'm going to let the new person take on as much as they want to and be there to keep things on the rails and make sure we get our deliverables in on time, but we'll have that conversation and figure this out.

The other nice thing here is that it's possible to set up multiple overlapping ranges that would be active at the same time, so for example if for some reason you wanted to have time between cracks, time after 2nd crack, and the combined time after first crack to the end (the sum of the previous two durations), that just works. You could do it in Typica 1.x as well, but not as nicely.

If there isn't a plan loaded, you don't get lines for ranges that haven't been activated yet and you don't get the non-existent planned durations. Similarly if you have a configured range that wouldn't have been activated in the loaded plan, that's also hidden. There's still some work that I need to do on this, but I'm hoping to get this finished before the next time I turn on the coffee roaster so I can test this.

This is the model behind the replacement for Typica's range timer or multi range timer. Notable features: instead of only showing one range, it shows all relevant configured ranges. If a plan is loaded, it shows the planned durations for each of these for ease of comparison. There's more context presented with the information so it's easier to tell what the indicator means. It's combined with the batch timer as I want all the timer related information to be clustered on screen.

Spending more time on the Typica 2 rewrite today. The feature that I'm working on today is more complex than the equivalent in Typica 1.x, but also I hope quite a bit more useful. Chipping away at it just a little at a time and testing that it's doing what I expect and so far it is.

One of the nice things about having been involved in developing professional development curricula for coffee roasting professionals is that I was able to learn about this sort of thing from several extremely qualified people earlier in the supply chain so I look at a contract that's not quite the same as what I normally get and I know what the words mean, why it was written like that, and what the implications of those terms are.

Got a couple new forward contracts to sign. I do these mainly to ensure availability of the coffee while still being able to spread the payments out over time so those are normally just written in terms of what the price is, but there's enough volatility that one of these is more directly tied to C futures and is written in terms that reflect that.

*hug*

Got $2 in the mail from someone who wanted to do a phone survey with a phone number that hasn't been associated with my address in over a decade. I'm inclined to pass on the $20 and not have my real number updated who knows where.

Started writing some code, but then realized that I hated the design of what I was about to flesh out, deleted what I wrote, and designed something nicer.