Knowledge Sharing & Mentoring Vocabulary | Pair Programming Exercises

1 / 5

A senior engineer is pairing with a junior engineer to explain an unfamiliar codebase.

Which teaching approach in pairing is most effective?

"Guided tour while junior drives" produces active learning rather than passive observation:

Approach	Junior's role	Learning quality
Senior drives, explains	Passive observer	Lower retention — watches but doesn't do
Senior explains verbally only	Listener, note-taker	Abstract — no hands-on connection
Junior reads alone first	Solo learner	Misses context that only the senior has
C ✓ — Junior drives, senior narrates	Active navigator + typist	Processes by doing while receiving context

Key vocabulary: "guided exploration", "narrate while they drive", "hands-on learning", "context layering".

2 / 5

During pairing, your partner doesn't understand a concept you introduced.

Which explanation technique is most effective?

Analogy-based explanation makes abstract concepts tangible through familiar comparison:

Technique	Why it fails or works
Sending to docs	Ends the explanation — transfers responsibility, doesn't teach
"You'll get it eventually"	Dismissive — leaves confusion unresolved now
Full theory first	Over-explains — too much abstraction before grounding in the specific case
A ✓ — Analogy + connect to code	Concrete, relatable, immediately connected to what they're looking at

Key vocabulary: "analogy", "concrete example", "relate to something familiar", "just-in-time explanation".

3 / 5

"I'd like to understand your existing mental model before I explain."

Why does a senior engineer check the listener's mental model first?

Checking the mental model enables a targeted explanation — one that fills the specific gap rather than starting from scratch:

Outcome without check	Outcome with check
Explaining things already understood (patronising)	Build efficiently on what's already correct
Assuming foundations that don't exist (confusing)	Fill the exact gap — not a broader or narrower one
Missing the actual misconception	Correct the specific wrong assumption

Useful check phrase: "What's your current understanding of how X works?" Key vocabulary: "mental model check", "assess current understanding", "build on existing knowledge", "targeted explanation", "explain the delta".

4 / 5

After explaining a concept during pairing, you want to check if your partner understood.

Which check is most effective?

"Explain it back" is the Feynman technique applied to pairing comprehension checks:

Check type	What it reveals
"Did you understand?" / "Is that clear?" / "Any questions?"	Almost always gets "yes" — social pressure prevents "no" even when understanding is incomplete
B ✓ — "Explain it back in your own words"	Immediately reveals: gaps in understanding, misconceptions, partial comprehension

The quality of the explanation back tells you exactly what to rephrase. Key vocabulary: "explain it back", "in your own words", "Feynman technique", "comprehension check vs. yes/no question", "active understanding verification".

5 / 5

"I'm handing this part of the codebase over to you after today's session."

What should a knowledge handover during a pairing session cover?

A knowledge handover should prioritise context over code — what isn't obvious from reading the code is most valuable:

Handover item	Why it matters
Purpose and scope of the section	Frames all future decisions — what should and shouldn't go here
Non-obvious design decisions + reasoning	Prevents "why was this done this way?" reverse engineering
Known issues and danger zones	Protects the new owner from stepping on landmines
Go-to person for X	Enables escalation without starting from scratch

Key vocabulary: "knowledge handover", "design rationale", "non-obvious decisions", "known issues", "landmine documentation".