I think I mostly have the web radio project in a good place for the moment. I’ve made some tweaks to the styling and layout over the last day or two, but am resisting the urge to add more features.

I had been considering maybe doing more with integrating Mastodon-based discussion into the site, but I feel like it’s better to have that just stay on Mastodon and keep this site simple.

🔗 ongoing by Tim Bray · The Real GenAI Issue:

The business leaders pumping all this money of course don’t understand the technology. They’re doing this for exactly one reason: They think they can discard armies of employees and replace them with LLM services, at the cost of shipping shittier products. Do you think your management would spend that kind of money to help you with a quicker first draft or a summarized inbox?

🔗 Pressure on Substack – Pixel Envy:

It would be odd if the economics of Substack — a collection of writers and publications with paying subscribers — are somehow better than those of, say, a magazine publisher today — also a collection of writers and publications with paying subscribers. It does have a tech sheen and the vibe of social networking, though, and there are no printing costs.

Yet it is still another platform hosted elsewhere. It simplifies the process for writers, podcasters, video creators, and others to publish their work for money. But their stuff is still made available at the mercy of software they do not control — and I bet there will be a time when Substack decides to make a controversial platform-wide change some publishers will want to back away from. The pressure is already there.

I had a few thumb drives lying around that I wasn’t using for anything, and I found myself wondering if I could somehow use them to get more storage for my Raspberry Pi.

Turns out the answer is yes! Mergerfs did the trick, and took maybe ten minutes to get up and running. Of course, there’s no redundancy, so I’m screwed if one of the thumb drives fails, but for what it is, it’s pretty handy.

Someone at work was telling me the other day about how they had attended a demo of some LLM-powered tool that “will write documentation just from looking at all the code.” They went on to suggest that we could point this tool “at all the old legacy stuff that we don’t have people to support.”

“Why would we do that,” I asked. “Are we going to hire people to go read all that documentation?”