I'm part owner and roaster at a little coffee company in Wisconsin. Author of Typica, a popular free program used to capture and work with coffee roasting production records that's used at roasting companies all over the world. Volunteer on the Roasters Guild education committee. Available for paid coffee consulting, training, open source software development. Living with a cat who broke into my house and decided to stay. Likes: cute, travel, food. Dislikes: blinking lights.
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.
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.
Authenticity Problem
Bonus timelapse: https://www.peppercarrot.com/en/miniFantasyTheater/064.html#bonus
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.
Author of Typica software for coffee roasters.