Comment by raw_anon_1111
8 hours ago
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?
8 hours ago
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?
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.
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.
Every developer from the beginning of time thinks that when they come into a new company that everyone who came before them were idiots. Eventually we mature beyond that.
I worked for two companies as a lead and the first thing I did to make things better is - nothing. I asked questions and understand the why.
But what company have you worked for that you only have to understand code? There is code, underlying architecture, dependencies between teams, database schemas and the politics?