I have a GL.iNet travel router. When I am not travel, it connects to the router's second WAN port. If my main internet goes down, it takes me 30 seconds to tether my phone and failover manually. My carrier detects and throttles hotspot traffic by measuring packets TTL, so I tweaks the router's iptables to dodge that. Typically I get over 400 Mbps.

From time to time I get the itch to improve my home network uptime, and I have to keep reminding myself that the current setup is fine.

I used to be the cool tech guy in school because I memorized the tutorial to jailbreak iPhone or to cheat in games with a memory editor. You know, stuff like "when you see this screen, click that icon", "find row 5 and change the second value to 0", or "open terminal, copy paste this command and hit enter". I don't think I learned anything useful from those.

Capital One does this to me as well, but at least they make it clear so I actually understanding what they mean ("You haven't opened an email from us lately...").

It's fine, Capital One. I did open your emails, I just didn't load your shady tracking pixels.

A gitops repo can never be the reflection of the system's actual state. It's a desired state your humans want the system to reach eventually, sometimes defined very loosely. This is the idea since Weaveworks invented the term years ago. Unfortunately I admit it's not very intuitive, especially to engineers who are not super familiar with declarative systems.