2 ms·
If done wrong, it will feel like an extended interview. It should be in the tone that the junior has a person whose highest priority is to mentor them. Upper m
by muzani 9y ago
If done wrong, it will feel like an extended interview.
It should be in the tone that the junior has a person whose highest priority is to mentor them. Upper management feels this is a tremendous waste of resources, so the term often used for this is "pair programming".
It's a way to teach a lot of the design patterns like SOLID or teach architectures in the real world. Most of these things are habits.
Sometimes they could take days just figuring out the architecture of something (where the files are). Sometimes they're stuck trying to build or compile. Sometimes the codebase has a particularly buggy thing that nobody touches, or the documentation only exists in someone's head.
Once the junior is up to par, which might take 1-3 months, they can move back to single programming. A lot of the habits are already in place.