Like, you might have someone working on something in a new codebase but misunderstanding the architecture or just going in the wrong direction in general and a review is the best way to correct course before getting too far in
I think the article is suggesting this person should be pair programmed with until they understand the architecture and can be trusted to contribute correctly, and I actually kind of agree - it always feels terrible to tell someone a PR they've worked on possibly for days is completely the wrong direction, and arguably this is already 'too far in' if they're going to need to essentially start again.
Intervening earlier in the process should lead to less wasted effort overall, but people often seem to treat pair programming like its two people at 50% efficiency, when it actually saves a lot of cycle time on reviewing code.
Interesting, could be a move away from typewise, do you support their gestures? Left to delete and up for capitalised.