I wish it were that simple. As a person who genuinely enjoys being a data scientist, and practices all those skills in a project I create on my own: the industry says otherwise. Integrating a technology into your practice that takes nuance out of it, just really means that managers and c-suites are going to expect you to give more nuance to your choices (which they deadlocked you out of). ML DevOps for the last two years are just me integrating more services.

This was after they encouraged a certain "cool culture" for a couple of months due to the lack of direction. It was pretty funny that I did not only get micromanaged, but was told I did the wrong thing, and then asked to do a third job that was not my responsibility.

This is what we get now when we had developers band together with those who want to protect their "content" that is not valuable enough to be published directly, nor is it original; yet they want to make sure that no one takes their amateur work and makes money from it before they do. This is what we get for wanting to create artist protections without needing formal frameworks or policies: the creatives find a way to do something, and then the replicators find ways to use it en masse.

Protecting content was not an issue after SEO, or before online payments for reading articles online, nor was it ever really necessary. All they do is make sure that those who are motivated to copy their content find ways to do so, with a hassle.