Tailscale allowed me to setup everything at home and just plug them to their network in 5 mins.

Over time, it was impressive to see how much the output of the same prompt would differ between us, and it seems to be heavily influenced by the role of the user. I.e. answers coming from the agent of a Data Engineer, a Backend Engineer and a Domain Researcher would not be the same at all. Some of us use harnessing tools, some not, but regardless it we saw differences.

So, for example, when a backend engineer would send a question to a data engineer, there was *some* added value even when it was a lazy copy & paste.

We will still see several reports of over adoption, mistakes, regression… all will only serve to learn, refine, and hopefully regulate.

I think it’s pretty naive to expect the entire world will simply discard the technology and go back to having humans doing it all.

I’m almost sure that the system had some sort of local replication and versioning that was enough to deal with occasional deletions, rollbacks, and single non-widespread hardware failures, so only the very catastrophic scenario of losing all servers at the same time (that for sure wouldn’t happen anytime soon) was uncovered.

Isn’t the GP describing exactly that?

Most of my awkward moments happened with family members casually cruising on my background while someone else had the word. Usually they can hear when I’m speaking and don’t enter the room.

Life becomes way lighter when you realize other people are also smart and what you’re “fixing” can very likely be:

- something so unimportant that no one felt it was worthy working on

- something that was supposed to work like that, and you simply don’t agree and want to make it your way

That said, a catalog (which Delta also can have) helps a lot to keep things tidy. For example, I can write a dataset with Spark, transform it with dbt and a query engine (such as Trino) and consume the resulting dataset with any client that supports Iceberg. If I use a catalog, all happens without having to register the dataset location in each of these components.

Edit: quoted evil-nation since it’s a debatable term usually applied to any country not politically or culturally aligned with some intelligence activity presence.

I only do automations (no dashboards at all), and try to keep them as simple as possible. Once I feel I’m reaching diminishing returns territory, I stop.

Only use HA if I need to mix different vendors (e.g. turn on the hue lights if the tuya sensor switches to on) or if the vendor app/service has a limitation that doesn’t allow me to do what I want. For instance, I have some automations for my Mitsubishi airco units cause their app sucks. Otherwise I’ll just use the default app or service.

Only configure an integration if I’m going to use it in an automation; I have a bunch of integrations detected that I don’t configure.

I decided to follow these rules a couple of years back, and since then I could address all my needs with almost 0 maintenance.