Mentoring

Patterns & examples

Code review as teaching

Use comments to explain patterns and suggest alternatives.

• Good, "I see you're using a for-loop here. Have you considered using .map()? It's often more readable and avoids manual state management."
• Bad, "Use .map() here."

Setting learning goals

Help mentees define clear objectives for their growth.

• Pattern, Identify a skill gap, define a concrete project to practice it, and set a timeline for review.

Pairing as mentoring

Switch roles regularly between "driver" and "navigator" to ensure active participation.

• Example, Let the mentee drive while you navigate, providing high-level guidance and pointing out potential edge cases.

Anti-patterns to avoid

• ❌ The "Hero" complex, jumping in to fix every problem yourself. This prevents the mentee from learning through struggle.
• ❌ Pedantic reviews, focusing on trivial style issues rather than meaningful logic or architecture.
• ❌ Overwhelming feedback, giving too much criticism at once. Focus on the most important improvements first.
• ❌ Vague praise, saying "good job" without explaining what specifically was done well.

KB Reference

~/vaults/baphled/3. Resources/Knowledge Base/AI Development System/Skills/General-Cross-Cutting/Mentoring.md

Related skills

• pair-programming, for collaborative development.
• code-reviewer, for structured feedback.
• writing-style, for clear communication.
• clean-code, for teaching best practices.