I agree with most of this, but also wouldn't want OP to be afraid to ask questions. My most common source of frustration with junior devs is when they toil away

I agree with most of this, but also wouldn't want OP to be afraid to ask questions. My most common source of frustration with junior devs is when they toil away at something that's over their head for way too long before just asking a question. Often when you're quite new you don't know how much you don't know and might think if you just keep at it you'll eventually make progress, whereas in reality you're not even heading in the right direction. So yes, definitely write down every process and take notes on everything you learn. Also review and summarize your notes so they're actually useful. That way you hopefully won't often have to ask the same question twice. But any time you feel like you're spinning your wheels or are unsure what to do, I'd encourage going ahead and asking. Over time you can also probably identify who's best at answering what kinds of questions, ideally allowing you to ask the right people, while not pestering any one person too much. But keep in mind sometimes you can actually be saving the senior devs' time by asking a quick question early rather than having a bunch of wasted work or delays later on.