Neal Wilson ✅ @neal@social.typica.us

This is one of the things I like about writing my own software. When I run into a problem I can just fix it. Based on what I was seeing I had a very good guess at where the problem was, verified the root cause, developed enough of a fix to do what I was trying to do, and carried on with the work.

Needed to swap out one of my SQL queries because I'd failed to test an important edge case. The new query has its own potential failure mode that I need to test for and correct if my intuition is right about that, but the thing I've written for now lets me carry on with the work I need to get done today.

I don't normally do a light roast Sumatra, the one that arrived yesterday is really nice that way, at least on the cupping table. I'll run a production test batch and see what I think about that tomorrow.

New coffees have arrived so tomorrow I'll need to taste all of these.

Who in their right mind is replying to text message spam with something like yes I'd love to hire some rando spammer to remodel my bathroom instead of hitting report spam and block?

If I put that in along with other removed dependencies, it's a 62% reduction in binary size. I kind of wish I could get it down to "fits on a floppy" but that would be a lot more work than I want to put in right now.

The other nice thing about the alternative approach is that it would cut the download size of the binary builds roughly in half. It was already a lot smaller on that metric than less capable competing programs, but if I can make things work better and have an even smaller program I'd rather do that.

Did a bit of research and it looks like it might not be too much work to replace one of the more problematic dependencies in the code I've been working on lately with something that's a lot simpler. I'll have to do some work to prove that out, but it looks promising.

Today's block and report as spam was a text message wanting me to pay them for giving me a chance to say anti-social things on the news because apparently that's what being a thought leader is these days.

Got to tell the most recent roaster trainee that his work there is no longer negative value (as it is when close supervision is required) so he's getting a pay raise as well as what I'll be tracking for his next roasting related pay raise.

New battery installed and seems to be working. It apparently arrived at about 81% charge.

Installing that will have to wait until after work since the screws I need are at home.

Replacement laptop battery got delivered. It is much thinner than the one I've removed.

If the former is an improvement, I can shave off a few bytes of memory use and remove a config option that becomes unnecessary.

Didn't think I'd get much coding time in today but I did open up a section of code that had one thing where I wanted to change what the expected behavior was and I expected there was also a proper bug. For the former I did a quick and dirty fix that I'll need to clean up after at some point but which will let me see if I like the new behavior better. For the latter, I found the error in my reasoning and corrected that. Still need to build and test on both of those.

Thankfully the tracking direct from the company that's actually doing the work (rather than the company that's handling the billing and payments) does not indicate a temporal anomaly and has a plausible estimated delivery date in the future.

Freight tracking on my most recent coffee order indicates that the coffee was picked up, started moving across the country, then traveled back in time to be delivered a couple months before I ordered it. This most certainly did not happen.

Hi ${firstName!"},

*delete*

I have corn.