Thats a great idea, I didn't think of this because the team is so small I thought it might use up a lot of time but I suppose in the long run it would be a benefit.
I was in a situation where I was managing a junior developer and felt like I didn't have time to properly train him, so instead I was leaving tons of comments on merge requests in GitLab with explicit instructions on what to change (often literally "Change this line to say this instead" with a brief explanation why).
In hindsight, I think I would've been much better off in the long run if I spent the first few months doing a ton of pair programming. Your situation seems a bit different, but I'd say it's at least worth a shot.
In hindsight, I think I would've been much better off in the long run if I spent the first few months doing a ton of pair programming. Your situation seems a bit different, but I'd say it's at least worth a shot.