AeroNotix

The reason you like it is the same reason people in customer service like it, too, they can do their job with less effort and coast on middling skill for longer.

Makes you wonder if they asked their agent to formally prove it with TLA+ and it just responded that it had performed the proofing.

It's the old infinite monkeys typing on type writers except now it displaces an entire industry and the only people profiting are the ones holding the tech that powers it.

Not sure if there are multiple products called "Timelines" but I can access my timeline on maps.google.com just fine and it has all my latest data.

I feel you. I've written quite a lot of Common Lisp over the years and I've tried to show off its capabilities to co-workers, often in comparison to the language used that that job.

Often I just get "huh, that's neat, now let's get back to mining the coalface".

I think the biggest issues involved around knowledge/skills/intelligence being potentially linked to genetics is that it often draws the eugenics proponents into the discussion and it's obvious how that conversation ends.

Even in binary you can see patterns. Not saying it's perfect to show binary diffs (but it is better than showing nothing) but I know even my slow mammalian brain can spot obvious human readable characters in various binary encoding formats. If I see a few in a row which doesn't make sense, why wouldn't I poke it?

Pure speculation but my guess is a specific state actor ahem is looking for developers innocently working with open source to then strongarm them into doing stuff like this.

Most editors these days should have "rename" functionality which is very aware of how that symbol is used across a codebase.

M-x lsp-rename in emacs, for example works great, if you're using lsp.

I find the standard blackbox_exporter far too limiting and static so I wrote an exporter which queries DNS zones from the Google API and creates targets dynamically from that.

It also has a feature which will query internal databases to find expected targets (kinda like service discovery). This covers more specific checks than what the DNS-based targets will provide.

These together mean that essentially no endpoint in our infrastructure is missing from being monitored in some fashion.

The exporter performs SSL checks (lifetime remaining etc) as well as providing HTTP/TCP latency metrics.

Not American but I can't stand using the toilet in places which don't have bidets. I feel disgusting and it ruins my day completely. I'd rather be uncomfortable and wait til I'm home or not go out.

I think this mostly comes down to whether applications can handle downtime if their workloads are restarted, scale up/down based on demand.

It happens shockingly often that applications only support working with a single replica and even worse when those applications cannot run concurrently with replicas of themselves which prevent smooth rolling updates.

IME if applications are fault tolerant of restarts, or support concurrent replicas then scaling up and down to meet demand is absolutely fine.

I wonder if it's related to the fact stoners are likely to go to bed on time.

That's just kicking the can over to an object storage API instead of managing disks.