3 is a common anti-pattern among software systems without clear leadership. Absent a steady, guiding hand, developers behind a component of a system are forced

3 is a common anti-pattern among software systems without clear leadership. Absent a steady, guiding hand, developers behind a component of a system are forced to set their own direction. Unfortunately, that direction stems from their motivation which is easily tainted by group ego. Maybe the developers feel like they're not getting the attention they deserve, maybe they have a big idea they want to solve and their tool is tangentially related. Or maybe they know exactly what to do, and the "other" people in the system do not. Whatever the rationalization is, it's enough to transmute their original purpose into a larger mission that everyone in their little silo agrees with, and that gradually diverges them from the rest of the system. "We're necessary and therefore we're important... more important than the system we were built for!" Eventually, a new name springs forth to signal their existence or even assert their dominance over the system to which they belong. The kind of thinking that plagued ParrotVM: https://news.ycombinator.com/item?id=7358646 https://news.ycombinator.com/item?id=7358646