My production database has been growing at a very stable rate of about 1GB per year (over the past 20 years). I have some thoughts about ways to shrink that, but will want to do some testing before rolling any such changes out. Realistically the database is already doing some compression so it's unclear if there are gains that are worth it.
This morning's coding session was heavy on bit level operations. The hardware documentation is suggestive (without going so far as actually having coding advice) of just using a lookup table for the command strings, but creating these directly by ORing together the right binary literals saves about 60 bytes in executable size and reads a little more clearly to me. (Clearly the engineer who designed the comms protocol thought about this approach and it just wasn''t put in the documentation)
uspol
Trying to buy more coffee. There'll have to be a price increase on the next Guatemalan coffee we bring in and part of that is the 10% tariff (which means a more than 10% increase that needs to be passed along since coffee weighs less after I roast it) while another part of that is just that the coffee is more expensive than usual.
Set up a new credit card terminal at the shop. Increasing sliminess and the poor quality of the latest hardware change we were forced into means that we've gone with a different company. Fortunately, we have employees and customers who have experience in their other businesses using this provider because "No Training Required" really means "We can't be bothered to provide comprehensive documentation that might scare people off".
Author of Typica software for coffee roasters.