AI might be great. AI might be terrible. I'm not all convinced that most data aggregation features baked into AI and used by most normal companies couldn't be implemented in R or SQL (disclaimer: I couldn't code my way out of a wet paper bag if the tool I was told to use was an axe). It's just wanted so that someone can crawl over data sets to ask simple questions like 'how many merchants exceeded n number of transactions between a and b date' or 'My customer needs an eIDAS certificate. What do I ask them to send us without having to talk to Captain Obvious?'. I mean, we're busting a gut on revamping our developer docs, but given that the spec is already public, I'm pretty sure that developers can already vibe code against that. Going to test that and see how it gets on.
That said, as I work from home, my work laptop lid remains closed for all but a fortnightly company all-hands meeting, and I ensure that I keep zero personal data on it. I'd be an absolute no if the demand ever morphed to always on video or activity trackers. That's a bridge too far.
As it stands, I understand the need for some policy enforcement/remote control of their assets, but will make whatever moves I must to ensure that policy doesn't infringe on the rest of my environment.
At the end of the day, it takes a certain kind of mind to like vi, and if you're not of that mind, you probably never will be.
To cover most uses, I'd suggest looking at SonarQube (most popular, not a fan), CodeClimate - metrics and quality and Codacy.
One thing to remember is that you do need to treat your servers as "cloud servers" in the sense that you should be able to re-generate your entire setup from your configuration at any time, given a bunch of IPs with freshly-installed base OSs. That means ansible or something similar.
If you insist on using cloud (virtual) servers, do yourself a favor and use DigitalOcean, it is simple and direct and will let you keep your sanity. I use DO as a third-tier disaster recovery scenario, with terraform for bringing up the cluster and the same ansible setup for setting everything up.
I am amused by the section about not making friends saying this :-) — most developer communities tend to develop a herd mentality, where something is either all the rage, or is "dead", and people are afraid to use their brains to experiment and make rational decisions.
Me, I'm rather happy that my competitors fight with AWS/Azure access rights management systems, pay a lot of money for hosting and network bandwith, and then waste time on Kubernetes because it's all the rage. I'll stick to my boring JVM-hosted Clojure monolith, deployed via ansible to a cluster of physical servers and live well off the revenue from my business.