Neal Wilson ✅ @neal@social.typica.us

Waiting for the furnace repair person again. Yesterday's repair took it from not working at all to it worked until I went to sleep last night but then this morning the house was cold again and it's working intermittently for a few minutes every few hours so hopefully it can get fixed for real this time.

I have working heat again. I stalled on getting someone out because space heaters were good enough to get through to when I had a scheduled work from home day instead of trying to work something in on a day when things are already short staffed.

Exported my Tinyletter subscriber lists (I had 3 accounts there for different projects). I still need to update the web sites to remove the signups and figure out what I'm going to do for future list mailings.

@gnomon What do we get if we use nano?

Today seems to be decaf roasting day.

Every time I encounter something cricket related I become more convinced that it can't possibly be a real sport that anybody seriously plays, but is instead some kind of weird long running experimental theater project that's exceeded the expectations of anybody involved in it.

@Taweret@octodon.social I like a bigger plush seal for that.

Me: *trying to use a laptop on my lap*
Cat: *trying to sit on my lap*

@mhoye I think they just show you the first half of that episode of the Garfield cartoon where everybody just does whatever the helpful lady in the phone tells them to do and says that this is the blueprint for the future of humanity that we should be working toward.

In unrelated news, I need to schedule a furnace repair at home. Looks like it's probably the capacitor on the fan.

If it weren't for the accuracy issue, I wouldn't have bothered.

The difference is that the old code was using something considerably more heavyweight to start with that has a lot of capabilities that aren't needed for this feature. My excuse is that this was already there and needed for other things and hundreds of microseconds is still plenty fast enough for this, whereas the new code does a lot less and it was a few hundred SLoC that I had to write, though I did encapsulate that such that it's almost exactly the same code at the call site.

For the most common use case it's running in almost exactly 1/10th the time.

Finished integrating the new evaluator for mathable fields in Typica 2 and did some performance testing. Despite the utter garbage quality of my code with considerable room for performance optimizations when I'm in a better head space for that, it's producing results that are always correct in 10s of microseconds where the old code was producing results that were only almost always correct in hundreds of microseconds.

Note to self: when dealing with linker errors that should be impossible, try "make clean" first.

Today's scheduled work from home day turned into a show up for a split shift day, but when I got home after the first chunk of work the neighbor's tree was no longer in my yard and there was a big fat bird hanging out there instead.

I think I've just decided that we never got any Final Fantasy games other than 1-6 and confusingly, 9. A shame they stopped making those.

Any performance difference is not all that important here because it's for low volume interactive use and either would give apparently instant results even on machines that would have been considered low end a couple decades ago, so it's really just personal curiosity.

Finished up some code that I've only been able to get a bit of time here and there to chip away at which would have gotten done a lot faster with a larger contiguous block of time to write it in. Kind of want to benchmark it against the code that it's replacing because on the one hand what I just wrote is not even remotely optimized, but on the other hand it does way less than the code it's replacing.