Evaluated roast progressions on two more coffees from recent shipments, but I don't have time to do production test batches today and have tomorrow scheduled as a work from home day (might come in after closing anyway to do some equipment maintenance that's hard to do when the shop is open) so I'll delay getting those out on the shelf for a couple more days.
@gnomon I even had the escape character that needed to precede the missing quote character.
One of my suppliers seems to have made their web site worse. They used to have a very good CSS for printing orders that saved on both toner and paper. That's been replaced with a slightly worse in both areas PDF download that takes too many clicks to get and printing directly from the web page is just awful in paper waste now.
work, computer touching, positive
@gnomon Classic space vs. time trade off. A few extra bytes of state instead of recalculating unchanged values in a loop.
work, computer touching, positive
@gnomon That's always a good feeling. I did similar the other day, taking my original code from ~56 seconds (unacceptable for something that's supposed to be interactive) down to about ~100ms (probably still has some room for improvement but at least it's usable now).
Took an initial crack at solving the real problem and while I still need to go back and make some changes elsewhere in the program to make this do the right thing all the time, the test cases I've been using to diagnose the performance issue are now finishing in about a tenth of a second instead of taking almost a minute and that's honestly good enough.
Author of Typica software for coffee roasters.