[array_key_first]

The main problem with having only seniors is that seniors have many many blindspots. Just by the nature of being there a while, they've built up hundreds of automatic processes that allow them to ignore or work around bad things at the company. In terms of code, tech, relationships, product vision, etc. It's the same reason why telling engineers to QA their own shit is a recipe for disaster. You need fresh perspective.

[raw_anon_1111]

Who would better be able to see those blind spots - a junior developer with no experience or a mid level or senior developer coming in with a fresh set of eyes?

[vineyardmike]

Fresh eyes are always better equipped to ask “Why” to poke at (no longer necessary) Cheshire Fences. Their ignorance (by virtue of being new) gives them cover to question things. This doesn’t necessarily mean inexperienced people, but that does give even more cover to ask the very necessary “why” and get answers, and excuses their lack of familiarity to intuit the situation.

Junior people also tend to have the humility to know they’re inexperienced and lacking insight, so they tend to be more willing to “follow” the senior employees rather than attempt to leave their mark as a leader. “Too many cooks in the kitchen” and all that jazz.

[array_key_first]

A junior, they have no baggage. Most software is unbelievably bad - almost all those seniors are come from products and companies that are horribly mismanaged, just in different ways. Or, maybe, the same way.