475: Invisible Mentorship

What It Covers

Sally Hall and Adji Slater explore effective mentorship techniques for developers with different experience levels, focusing on code review feedback, balancing consistency with team morale, and adapting communication styles to individual needs.

Key Questions Answered

• •Code Review Timing: Avoid in-depth technical discussions during urgent bug fixes or late Friday afternoons when developers lack mental capacity to learn. Save larger conversations about testing philosophy or architecture patterns for dedicated team discussions instead.
• •Draft PR Strategy: Use draft pull requests to solicit early feedback on uncertain implementations rather than presenting finished work. This approach helps reluctant collaborators engage more readily by framing requests as seeking input rather than demanding help with decisions.
• •Feedback Calibration: Match feedback intensity to developer confidence levels by monitoring PR comment volume. When multiple review rounds have already occurred, skip non-blocking nitpicks to let developers complete tasks successfully rather than eroding confidence through endless revision cycles.
• •Assumption Management: Prefix technical terms with links or spell out acronyms on first use to accommodate varying knowledge levels. Use phrases like "you probably already know this" before explanations to respect expertise while ensuring shared understanding across experience gaps.