Eh, the problem with the "IT department dictates all the choices because the devs are stupid" approach is that it takes ownership away from the devs, therefore leading to a self-fulfilling prophecy. If I can't be trusted to make technology decisions for the system I know about (and the IT department knows nothing about), then why should I care about delivering the best possible product?
Sorry, I've seen exactly that pattern happen in my (still) current company and it just leads to teams that are completely unable to think for themselves and work like machines in a cog.
I'm not saying company guidelines shouldn't exist or that you should allow a proliferation of 200 different programming languages, but I have never seen the "devs are stupid" approach work; if this is indeed a problem in your org, hire better people! (Which doesn't mean: smarter hackers. It means: responsible, professional individuals that work well together in a highly effective team and can be trusted to make decisions in the best interest of the product.)
Sorry, I've seen exactly that pattern happen in my (still) current company and it just leads to teams that are completely unable to think for themselves and work like machines in a cog.
I'm not saying company guidelines shouldn't exist or that you should allow a proliferation of 200 different programming languages, but I have never seen the "devs are stupid" approach work; if this is indeed a problem in your org, hire better people! (Which doesn't mean: smarter hackers. It means: responsible, professional individuals that work well together in a highly effective team and can be trusted to make decisions in the best interest of the product.)