Happy New Year! If you are a Fool, anyway, and I am. (Although Wikipedia claims that this idea -- that April Fools Day originated from mocking people who celebrated it as the first day of the year -- is not entirely backed up by the evidence. Ah well, perhaps only Fools believe that story.)
An ok day at work today; we're all still getting used to the new normal, and I have a pretty big backlog, which is annoyingly psychically burdensome, but is more like "ugh" levels than like "gah, total despair" levels. It's also been a weird week in other ways, with the kids' birthdays on Monday, some running around town driving Amy to a dental appointment on Tuesday, lunch with Matt today, just finding it a little hard to get into a rhythm. There's opportunities for things to get better, though, and I'm looking forward to trying to realize those.
A thing that happened in March that I forgot to mention: My uncle (my mom's sister's spouse) Tom died. :^( He'd been in and out of the hospital, and not in very good shape for a while, and was at home in hospice care for his last few days, so it wasn't sudden or shocking, but is still sad. My sister Aunt Jo is going to be in the US for a conference in the LA area at the start of April, and I'm meeting her there to have dinner with our dad, and then we're both going up to the SF area to spend some time with our aunt, a couple of days for me and a couple of weeks for her. There'll be a memorial ("celebration of life"? are those the same thing or subtly different?) at some point, not sure yet when.
Another thing that happened in March is that I've been doing more with "AI" at work; it's been a general push from the company for a while, and I am somewhat eye-rolling about it, but the rest of my immediate team (DevOps) mostly shares my views about it, and we're working together to come up with ways to use it in ways that seem safe and effective. Software Engineer (SWE) type folks are somewhat more free to just turn it loose and see what happens; we can't risk doing that in situations where it has access to our credentials that let us do things like destroy production databases, so we have to be a bit less zealously enthusiastic than those folks. One distinction I've enjoyed recently is using it at build time, when you can ask it how to do things, and help craft scripts andn stuff; vs using it at run time, like having it do things in automated pipelines. We're much more comfortable with the idea of AI-written things in pipelines (which we can review and understand) than we are with just letting it do stuff on the fly. Anyway, I know everyone hates AI in general, but it is in fact a pretty powerful tool (at least when your company is paying for high-end versions of it -- oh, and another advantage of the build-time approach is that we still have the scripts even if (when) the pricing realigns to match the actual costs), if you are in fact competent enough to handle power tools.