+1 to this.
I used to work with a guy like that and it created a ton of tech debt. He would write new services using a new technology for each one, not to documenting or maintaining any of them.
I used to work with a guy like that and it created a ton of tech debt. He would write new services using a new technology for each one, not to documenting or maintaining any of them.
Neomaniacs gonna succumb to neomania. The bigger question is why the system permits that, rather than steer those urges to try something new into useful experiments that might advance the status quo.
Giving employees opportunities for side projects helps somewhat. Allowing for gradual migrations to new technologies helps as well.
In a friend's company, their CTO has mandated a rewrite of the backend in Clojure, and that it should be as asynchronous as possible.
Low and behold, the devs aren't familiar with the language, and the async has resulted in a host of heisenbugs, that are hard to reproduce.
On the CTOs resume though, he would show how he got the shiny new architecture rewrite, any problems were the devs fault.