I started doing similar changes because software became a shitshow. Corporate software shops are just a bunch of IT people trying to get their friend's product

I started doing similar changes because software became a shitshow. Corporate software shops are just a bunch of IT people trying to get their friend's products in use in the company for kickbacks. So what you have are multiple IT teams with more power than developers trying to tell everyone which tools they MUST use. Developers at the last place I worked had no access to production, could not deploy code at all, could not test their own code, could not even push code, could not see other team's code, etc, etc. But, the company had a devops team, a team called "app ops", a "SRE" team, an IT team, an "infra" team, and a security team that strangely was dictating which tools were used to deploy code. NONE of these teams did anything remotely close to what their team name did. They would do visibility projects which, oddly, sometimes involved developing software but not the kind that generates revenue. "dev ops" would deploy software to production, if they had time between their projects. "app ops" was supposed to handle support incidents, if they had time between their projects, etc... It is useless to try to build software in this environment. It is far easier to build a hunk of wood and say, "here you fucking go, take it or leave it" than to deal with dozens and dozens of people trying to extract money from the development process while suffocating the company.