[gregkerzhner]

I would argue that those "hours wasting time" looking for an answer yourself before you give up and ask someone more senior aren't a waste - they are an invaluable part of becoming senior yourself.

As a senior engineer, you will often spend hours and days stuck trying to solve hard problems with noone else to ask, and having the grit, determination and creativity to do this is one of the greatest skills you can teach an engineer. Having barriers and friction in the name of this self sufficiency is totally fine and likely beneficial to the development of a junior dev.

[avmich]

I would argue that those hours can really be wasted. Yes, learning the system brings long-term benefits. But the way the system is learned can be of different effectiveness, significantly different.

Having a lot of questions could mean, that the onboarding isn't set right - and this can very significantly influence the developer productivity, even middle-term.

That doesn't mean the newcomer doesn't need to think or is allowed to abuse the system :) - in my experience, the situations when the questions are legitimate are just too frequent, so it makes sense to not consider questions undeserved out of hand.

[rramadass]

Absolutely correct!

>you will often spend hours and days stuck trying to solve hard problems with noone else to ask, and having the grit, determination and creativity to do this is one of the greatest skills you can teach an engineer

I would argue that _is_ the very definition of an Engineer.

Also it is an invaluable necessary skill to cultivate to navigate Life itself.