My experience is that it works until it does not, and then you are down on a rabbit hole trying to figure out why.
The only reason we keep using it is because we have other priorities, but once we have more spare time, this module is going to hell, it's not reliable at all.
the main question here is, do you really need to change the settings once you have a baseline?
I'm another one using a private GitHub repo for this. But I don't need to pull, update, sync or whatsoever. I've been using the same config for years, and in the eventual case that I would change / add something, I can do that quickly in a few computers, no need to have any sort of sync.
For VSCode settings I just use the built-in service.
As you said, a benefit of large distributed systems is that usually its a shared responsibility, with different teams owning different services.
The exhaustion comes into place when those services are not really independent, or when the responsibility is not really shared, which in turn is just a worse version of a typical system maintained by sysadmins.
One thing that helps is bring the DevOps culture into the company, but the right way. It's not just about "oh cool we are now agile and deploy a few times a day", it's all down to shared responsibility.
I've been using a LG 27" 4k60Hz with a MBP for a few years.
Recently got a 32" LG monitor from my employer, and I really tried to make it work, but it was plain impossible. It's too big, and due to scaling (which I don't need with 27"), fonts are very blurry.
I ended up with my 27" again and using the 32" for my bike trainer :)
There is no one better than yourself to get what you're looking for, so instead of relying in a third party to give you the edge, make sure you're already on the top of the wave.
I never work with external recruiters (staffing agencies)I have made the exception three times, and all of them ended with a poor experience, basically repeating the same information over and over again between them and the people from the actual company.
> If somebody asked me logic/brainteaser questions like that, I would politely stop them, explain that if they're asking me that question I'm not a good match for the company
This is exactly what I started to do after I was asked a leetcode-based question for a SRE manager position.
It turned out that by making clear my "profile", I stopped to have bullshit interviews and started to get ones more aligned to actual daily work.
By contrast, I have recently accepted a new position, and in almost every interview I was asked, with a negative connotation, why I had stayed so long (6 years) with my current employer.
If something fails and you don't have idle runners (hence wasting unnecessary resources), things start to snowball.