The situation with the fireworks is particularly bad entirely because the police always try to direct traffic and they don't do this enough to be good at it so it's quite a bit faster for me to just walk. (Seriously cops, stop it, there'd be way less congestion if you just let people take the routes they want instead of funneling everybody out to the other side of town before letting them turn around and get back to where they're trying to go)
USPS keeps trying to sell me on "enhanced" click-n-ship. The problem is that it's a massive usability downgrade from the non-enhanced version, at least when it comes to my primary use case. So much so that I'll probably end up writing my own thing instead of trying to train people on the mess USPS made.
Ignoring a wholesale request email for several red flags: No business name provided, residential address, lack of familiarity with offerings listed on web site, request for samples before seeing pricing, "lost" their previous coffee supplier, far enough away that they should really be trying to find someone closer to them anyway. Could be legit, but they're making themselves look like a scammer.
I don't know if anything is going to come out of it, but I seem to have started working on something that's sort of a hybrid between old style community forum software and long form blogging platform with specific affordances for communicating with data relevant to professional coffee roasters. Worst case I have some fun, learn some things, and toss the result, but even if all I really get out of it is a weird CMS for my other projects that might be useful enough.
For those wondering, the side jobs I pick are all cases where the company or non-profit or whatever organization is contacting me directly because they either already know who I am and what I can do or they've called around to people they know and got referred to me that way. (I've also done the you don't want to bring me on to this, because so and so is better on that thing.) A general recruiter isn't going to know enough to correctly identify anything I'd be interested in.
This one is geared toward experiment design and iterative profile development. People shouldn't use the new feature all the time, but it should be a good QoL improvement for people who need it while being ignorable for people who don't.
Started work on implementing what I think is probably the biggest feature for what I hope will be the next update to CRUCS, though there are a few things that I'd like to try to get into that. This involves one highly invasive change that I'll need to audit the whole (thankfully small) existing code base to make sure everything is updated to do things slightly differently and there's an aspect where I'll want to try a few different approaches to see what works best.
Author of Typica software for coffee roasters.