A simple on/off toggle isn't going to prevent them from using your data. If your data is in their server then it's going to be used one way or another. Whether in an anonymous way or shipped to where there are no privacy laws.
Yep, did the same thing too. It's nice that you just need one tool to unscrew, screw things and everything is labelled well that you don't need to go dig to multiple websites on how to do repair/replace parts.
But of all things, replacing keyboard was the most tedious one in framework with so many screws, haha.
It never occurred to me to lookup the creator of the tool[1] that I used to use so often. It's so easy to overlook that there are actually humans with their own story (tragic or not) behind the tools that we use.
I should learn to appreciate people behind the code more. And, I'm so sorry what you had to and are going through, Mr. Meyer.
And the reason they suck is the feedback loop is just too high as compared to running it locally. You have to jump through hoops to debug/troubleshoot your code or any issues that you come across between your code and output of your code. And it's almost impossible to work on things when you have spotty internet.
I haven't worked on extremely sensitive data but for PII data from prod to dev, scrubbing is a good practice to follow. This will vary based on the project/team you're on of course.
The developers also lack knowledge about the environment; can't evolve the environment; can't test the environment for bugs; and invariably interfere with each other because it's never isolated well. And also, yes, it adds lag.
Anyway, yes, working locally on false data that little resemblance to production still beats remote environments.