Neal Wilson ✅ @neal@social.typica.us

At the start of the day I had 13 to do items prior to getting a 1.0.0 release uploaded. Now that's down to 8 and there's a good chunk of day left to work on this, so I'm probably not getting this done today, but SOON™.

I'll still want to test how this works on Mac/Windows machines and with Safari/Edge, but I think I'm happy with the print layout for CRUCS now. The page fits roasting plans up to 20 minutes (longer on A4 paper) and if I were doing logging on paper I'd have plenty of space for data from a couple batches hand written next to the plan while still having lots of space for stuff like cupping notes or other kinds of batch details.

Today I'm working on adjusting the print styling for CRUCS. One of the major use cases I see for this is helping people who aren't using any kind of data logging software have access to good quality roasting plans and being able to just hit print, slap the page into a clipboard, and have something that's usable at the roaster that way is important.

Ran into a footgun on the latest chunk of code. Apparently the latest language update provides a different name for the thing I wanted it to do, but by the time I found that I'd already edited my code to work around what I'll argue was a bug in the language design.

Anyway, lots of progress on coding got done today. Added a bunch of previously missing controls, noticed and fixed a couple bugs. Still doing okay on focus so I'll keep going down the to do list a little longer and see how much I can slam out today.

The cat thinks it's very important to always be within petting range, just in case I happen to want to pet a cat.

There's a laptop on my lap so the cat is settling for being curled up next to me, still in petting range.

Email: We've noticed that you haven't opened our emails.
Me: Nice to know that my mail client isn't leaking the fact that I've opened your emails, but I'm fine with not getting them.

A roaster friend just reached out with a problem that the project I've been working on lately might be useful for sorting out, so despite the fact that I'm not satisfied with the current state of things, I've put up the very much WIP and have my first outside of my company tester. It's not really in such bad state as it sounds like there. I should just need a few good extended sessions to slam out the rest of my to do list.

Made some UI decisions today. Might change them later, but it's enough that I can build the features, see if that'll work well enough, and change it later if it turns out I've made a horrible mistake.

I don't understand puzzle naming.

I keep seeing what I assume is some kind of anti-spam detection technique of including a couple random lines that look like they came out of an 18th century melodrama and I can't imagine that actually works very well, yet I keep seeing it (I'm not using a spam detector).

Got one item off my to do list today.

Decided that between the fall promotion and current content it's fine for me to have a Paramount+ subscription for a little while. Is there a recommended viewing order for all of the Star Trek that came out after Enterprise? (currently going through Lower Decks)

Finishing up payment processing stuff for CRUCS today. I'm going with a pay what you want model for this where you can use it without paying for it, but I'll also accept money.

Taste testing yesterday's production test batches. These were roasted against plans adjusted in CRUCS (I copied in the milestones from the initial exploratory roast and then made adjustments intended to get something easier to do with a larger batch size and based on the initial sensory observations) and the results are quite nice.

Or at least that's what I would be working on, but the cat says no so I guess I'll have to finish that up later. A nice side effect is that the settings fields will start out displaying their current values instead of whatever the browser feels like inappropriately auto-filling (Firefox wants to do crazy things when I change the forms).

Working on adding settings persistence to CRUCS using Window.localStorage. For example, I have graph defaults set to 20 minutes by 500F which is a nice safe default for most of the roasting machines still running, but there are also a lot of faster machines being operated by people who don't need a duration that long or people who prefer °C. They can change their preferred settings once and CRUCS will keep the updated settings. Settings (or anything else) are never sent back to the server.

Left the cat curled up in a blanket when I went in to work. Got home to find her in exactly the same spot. Of course, now that I'm back she wants to sit on me instead.

Tasted the test progression from the new coffee that got delivered the other day. Used the not quite finished yet CRUCS to make a couple tweaks to the plan before doing the production test. This is a lot faster than the old internal tool I made CRUCS to replace (I also wrote the old tool).