Neal Wilson ✅ @neal@social.typica.us

So whatever was causing the problem in the first place is may still be hiding somewhere unfixed just no longer causing directly visible problems. I'll use it the next time I roast coffee and see how that goes, but this is something I'll want to come back to later to clean things up properly.

Just did my least favorite kind of bug fix. Gave up on trying to figure out why the erroneous behavior was happening (a variable was being updated with double the expected offset) and rewrote the code to just recalculate the value every time it's needed, at which point everything seemed to start working properly. It's a cheap calculation infrequently performed so it's not like anybody will notice, but I kind of hate that a change that shouldn't have altered the behavior at all ended up fixing it

Lots of big dogs out today.