Moreover, I've used minute-by-minute forecasts myself, and (at least where I lived at the time) they were quite accurate. My use case was "where is a 30 minute gap when I can walk home without getting soaked", and I never once got soaked. So much of the OP falls into the category of things-I-know-to-be-false-from-experience.

The article really has a strong vibe of "algorithms are faulty, we need humans in the loop to make sure they're behaving well!", with a hidden assumption of "humans are less faulty than algorithms". That's an empirical assertion to be determined on a domain-by-domain basis. It's certainly true that having a human in the loop leads to worse outcomes in chess (unless the human has enough modesty to just not do anything). The same is increasingly true of other domains as well.

Perhaps someday, incorrect, largely content-free FUD articles about how algorithms suck will themselves be written entirely by algorithms.

This is pushing way too many of my buttons, so I'll just close by pointing out (on the other side of the apps/humans scale) that a substantial fraction of the time, when I check the weather on NWS, it says something like "Today's high: 56; current temperature: 58". I certainly hope that a human in the loop would fix that problem.