Neal Wilson ✅ @neal@social.typica.us

Tracked down a math bug that I'm shocked I didn't see sooner (outputs under certain conditions are very obviously wrong). The C++ code I based this on had it right and I broke it during the porting to Javascript. Accidentally used the same index twice instead two different indices for one of the intermediate calculations.

Finished most of my travel arrangements. All that's left is sorting out when I'm dropping the cat off with my mother (fresh cat supplies are ready to go) and figuring out if my sister is going to do the airport drop off/pick up so she can use my car while I'm out of town (hers is getting an engine replaced) or if I'm just leaving it parked at the airport. She wants to stall on making that decision as long as possible.

What is it with Paramount Plus deciding that I really want to watch the next episode of something in Brazilian Portuguese? Yes, I've been to Brazil a few times, but I'm not anywhere near fluent.

Someone from what my phone says is a California number just left modem screams as a voicemail for me. I hope that's not set to automatically retry.

Edge on Windows prints only a tiny bit smaller than Firefox on Linux, so I'm going to call this working acceptably for now.

It is Safari 13.1.2 which is a few years old now, and what it's choking on is kind of fundamental to this working at all so I'm not going to go out of my way to fix that.

Mac test: I don't have an up to date Mac, but the old one that's convenient to test on shows that it's completely broken on the version of Safari that's there (literally nothing at all works). Firefox is fine, but prints the table a little smaller. Still wide enough spacing that I would be comfortable writing on this at the roaster.

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.