In the 35+ years, I have spent in IT, operations, and application development, the basics have not changed too much. What has changed is the jargon. It’s like education. Every so often, somebody or a group of people, come out with a New and Improved method of teaching. After all, is said and done, after we get through the jargon, teaching students is still the goal.

While there is some exchange of ideas and some cooperation, ultimately it is still the developers who develop applications and operations run or implements them. There is a natural progression of steps in the process of developing applications. The steps have to be followed in order and no steps can be bypassed or short-circuited.

“Continuous Integration”
While that sounds great in the propaganda, in practice not so much. Have you ever heard the saying that “Too many cooks spoil the meal”? Having people each working on developing a part of an application speeds up the development process but a lot of that time is wasted on meetings to coordinate that development. Ultimately only one individual must be responsible for the decisions.

“Continuous Testing”
“to identify bugs and potential risks in the early stages of the software development lifecycle in order to minimize errors that would manifest in the end product” is a semantically null marketing phrase. While various modules of an application can be tested as they are developed, the ENTIRE application must be tested before it is put into production and that testing cannot be done until ALL the coding is finished.

“By monitoring and analyzing data and logs generated by applications, developers can easily get insights into how features or configurations impact users.”
You can monitor and analyze ad nauseam in the shop but it is ultimately the users that tell you how they are impacted. And the user is ALWAYS right, even when they are wrong.

“Collaboration between development & operation teams translates to joint responsibility”
Which translates to time-wasting, counterproductive finger-pointing when something goes wrong.

Last but not least. No matter what testing software a developer uses, no matter how much testing is done, no matter how much idiot-proofing a developer does, it’s never enough. There are many times more users than there are developers and testers and users, whether inadvertently or by design, sometimes use applications in ways they were not designed to be used.