I do not share the same experience. I've recently mentored someone from knew nothing about git up to
- what is version control [0]
- good commits and good pull requests
- working through pull request reviews [1]
- merging my PR into their PR [2]
- how to edit config files in a sane way (naming conventions are important)
- how to debug a few weird Arma3 config file errors
- how to deliver changes that satisfy some ... specific community constraints
- ways to think about solving a problem, before actually trying to solve it, and why
... and a bunch more. All on discord.
Direct messages. Audio only calls hanging out for a few hours talking / sharing screens, sometimes pair-programming. If I'm busy, I find some relevant documentation and ask them to read through it until I've got a chance to speak to them. A big mix of async and sync communication. Sometimes organised, sometimes ad-hoc.
I've got workshops mentally planned out to upskill the rest of the game server dev team. I've got another mentoring project lined up where we'll hopefully be able to dive into some functional programming things [3].
Remote mentorship isn't tough. It just requires
1. Prioritising the DMs from the people currently being mentored.
2. Manually creating the "sit next to each other and work on something" opportunities by clicking like four buttons to start a voice call and jump into it.
In essence, I make them the person sitting next to me in my online Discord office.
----
[0]: the "keeping a version of every single change in any tracked project file" lightbulb moment was fantastic to see.
[1]: the "always expect someone else to find something wrong because you're a human being who inevitably gets tunnel vision" lesson.
[2]: the "i'm going to make you responsible for merging into release branches at some point, so let's get you comfortable with it now" lesson
[3]: the person wants to learn how to be a "scripter", whereas the previous person was a Arma3 3DEN Editor main.