Came to comments basically to say this. I have seen too many shops victimized by their develops... "letting the inmates run the asylum". Too often, an org has promoted someone who is, at *best*, a "senior developer" to a position like Architect, Chief Architect, etc. and allowed this person who effectively has 2 - 5 years' of experience... repeated 1 - 10 times... making decisions far outside their knowledge, capabilities, foresight, etc. with no regard for a ton of non-technical needs and requirements. This person too often makes decisions based on things like "do I personally like working with this tool?" and "is this tool going to look good on my resume?" and "what semi-celebrity guru Internet expert loves this technology?" rather than "Does this meet our needs? Does it run well in our target environment? Is it secure, mature, and stable?" and so on. And then the business finds themselves in a situation where they dumped a ton of time and money into writing code using a toolchain that will never get them to the finish line, or that slows them down, or whatever. To make it worse, these orgs often end up chasing "new and shiny", constantly rewriting code that was already working, or maybe "almost working good enough, we guess", using new toolchains that the developers swear "this is what we need to solve the problems!" instead of actually moving on to new initiatives.

J.Ja