I think this needs to explicitly be handled by a role in the team. A common team might comprise of a project manager, architect, 1 to 4 more senior devs, some r

I think this needs to explicitly be handled by a role in the team. A common team might comprise of a project manager, architect, 1 to 4 more senior devs, some representation from a test team, and a number of juniors, interns etc. One of the senior devs needs to handle onboarding new people and communicating the ideas of the architects and seniors over and over again to juniors. This is tiresome and boring to some. You need patience and empathy. It can be fun though as you get to meet lots of people and help them when they need it most. Most importantly you give the other seniors the time to work, without them getting involved in yeah just "make clean build" that away type issues. I actually like the role and if the team doesn't have too much churn, you're just another senior dev.