I've been attempting to communicate this to places I've worked at for more than half a decade (since the trend seems to have taken off). I've only been met with

I've been attempting to communicate this to places I've worked at for more than half a decade (since the trend seems to have taken off). I've only been met with skepticism, and cynicism, on behalf of management, implying I'm too lazy or something. There is a good analogy in science - theory vs. experiments. Software applications are theories, and testing them are the experiments that confirm that the theory works. It's important to separate the two in order to minimize bias, but also to allow each side to specialize and optimize accordingly. The best developer experiences I've had, was when there was a clear delineation, and the testers had the ability to optimize their environments to catch even the slightest change or deviation in software behavior. Now, engineers are expected to do almost everything, at times even design as well. I don't understand this about the industry. Chefs aren't expected to be the host or run the tables. Commercial airline pilots aren't expected to check in the passengers or serve the food. There are of course exceptions to roles, but overall, most industries have defined roles. Somehow the software industry (at least web, in my experience) has blurred the lines and increased the number of responsibilities on the engineers, not to mention having the strange expectation to steer away from coding as you gain more and more experience.