jarofgreen

I wonder if pedantically speaking the definition of lake would include non-tidal in many countries but ....

A) humans use names sloppily and if it's an important detail I wouldn't assume a lake is non-tidal without checking.

B) non-tidal bodies of water might still change height over the year, for example after a heavy rainfall.

Mainly I'd question the need to automate it. It's difficult, and in many cases the cost of a human to drive it is tiny compared to all the other costs you need to pay so just do that (as in the article - those weren't automated). Also, driving them can be fun :-)

I've written in the past about these types of projects: https://opendataservices.coop/blog/2020/05/07/community-data...

The exetools website seems to be on its way out (domain for sale, no updates), which shows how hard it can be to get these types of projects to go well - I'm hoping I can help a bit!

So I set the script to also write out a metric that was just the time stamp the metrics were last updated. Then it was simple to set up an alert in Prometheus - I can't access the config now so you'll have to look it up yourself, but it was basically "alert if metric less than now minus a time gap"

Ok, maybe my suggestion is the wrong wording but I still think the original is confusing. If I'm going throught a process and suddenly get a confusing popup I didn't expect, my first instinct is I can press cancel and get back to what I was doing. But in this case it takes me out of the whole process.

But I'm not saying my UI choices are representative of all - really, it's about proper UI testing. The article doesn't say what user testing they did, if any.

I guess this falls into the trap a lot of tech metrics stuff falls into: ok, we can clearly show that sales of paper tickets fell. We assume there is a corresponding rise in card sales (But crucially, the article doesn't prove that). But what none of the stats can clearly show is whether people were happy with all this or not. Maybe they would have preferred the cheaper prices AND a paper ticket.

The article then goes on to make other points about AI and automation.

The way to do this in Prometheus is to use the following settings on the blackbox module:

    [ preferred_ip_protocol: <string> | default = "ip6" ]
    [ ip_protocol_fallback: <boolean> | default = true ]

So you need 2 modules, one for each ip version. As for automating setting these up, we deploy our Prometheus server with salt so we can use Jinja templating in all our Prometheus config files. That really cuts down on repeating boiler plate code.

This is also interesting for other reasons; in host downtime situations you can sometime see they will drop one type of traffic and not the other.

eg Your web browser will automatically save any URLs to it's history for any user of the computer to see but will ask first before saving passwords.

eg Any web proxies your traffic goes through or other software that's looking like virus scanners will probably log URLs but probably won't log form contents (yes HTTPS makes this one more complicated but still).

I've been working on a tool that treats the git repo as the SSOT then lets you dump out all kinds of formats for data work including a sqlite DB. I haven't had as much time as I would like on it but it's at https://pypi.org/project/DataTig/

"Banks and building societies are required by law to have a written complaints process which tells customers how to make a complaint."

Python has Celery, but maybe the author is looking for more choice between brokers. https://docs.celeryq.dev/en/stable/index.html

We also do something similar on Datatig, which is a tool I'm writing for the general situation of crowdsourcing data in Git repos. It makes it easier for people to submit data and then creates usable data and handy websites. The static website output has an API which is just static JSON files. https://pypi.org/project/DataTig/ or https://datatig.readthedocs.io/en/latest/

I once took a Python API with SQL Alchemy and took 30% of the speed by adding an eager load instruction to a query. Python profiling showed a lot of time in the ORM & database, then turning on SQL logging made the issue obvious.

Still feels like it should be called the "1 + N" problem tho. The 1 query happens first, then the N queries afterwards.

https://www.amazon.co.uk/password-book/s?k=password+book

Often people will mock them on social media for the likes, but actually in some circumstances ... I think they are the best option.

(They can be made stronger too - tell people to remember one word that they put in front of all their passwords but don't write down, like "cat". Then anyone who steals the book can't use it but they are still using different passwords for each site.)

Grep the open source project has spent years building up it's name and it's good will by being - as you point out - a great tool.

You are now attempting to claim some of that good will just by copying the name when you have nothing to do with grep.

If you did that to a commercial company they'd sue you for trademark infringement.

(Hopefully this is a serious enough point to not count as a "tangential annoyance")

> In a frozen vault in Houston sits the original NASA photographic film of the Apollo missions. For half a century, almost every image of the Moon landings publicly available was produced from a lower-quality copy of these originals.

> Now we can view them as never before. Expert image restorer Andy Saunders has taken newly available digital scans and, applying pain-staking care and cutting-edge enhancement techniques, he has created the highest quality Apollo photographs ever produced. Never-before-seen spacewalks and crystal-clear portraits of astronauts in their spacecraft, along with startling new visions of the Earth and the Moon, offer astounding new insight into one of our greatest endeavours.

I saw the exhibition in Glasgow, was good!