mentoring-developers

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Mentoring Developers

开发者指导

This skill provides frameworks for effective mentoring, knowledge transfer, and developing other engineers.

本技能提供用于高效指导、知识传递以及培养其他工程师的框架。

When to Use This Skill

何时使用本技能

Starting a formal or informal mentoring relationship
Onboarding a new team member
Teaching technical concepts to junior engineers
Running effective 1:1 meetings
Pair programming with less experienced developers
Helping someone navigate their career

开启正式或非正式的指导关系
新团队成员入职培训
向初级工程师教授技术概念
开展高效的一对一会议
与经验较浅的开发者进行结对编程
帮助他人规划职业发展

Core Frameworks

核心框架

Crawl-Walk-Run Progression

爬-走-跑进阶框架

A framework for teaching new skills progressively:

Phase	Mentor Role	Mentee Role	Duration
Crawl	Do, they observe	Watch and ask questions	Until they understand the "what"
Walk	Guide heavily	They try, you correct	Until they can do it with help
Run	Provide guardrails	They lead, you advise	Ongoing with decreasing support

一种逐步教授新技能的框架：

阶段	导师角色	学员角色	时长
爬	演示操作，让他们观察	观察并提问	直至他们理解核心内容
走	全程引导	尝试操作，导师纠错	直至他们能在协助下完成任务
跑	提供必要的指导边界	主导操作，导师提供建议	在逐步减少支持的前提下持续进行

Example: Teaching Code Review

示例：代码评审教学

Crawl: You review PRs together, thinking aloud about what you look for, why things matter, what makes good/bad code.

Walk: They do the review, you watch. You ask questions: "What about this section?" You course-correct in real-time.

Run: They review independently. You spot-check occasionally and discuss any disagreements. They come to you with edge cases.

Key principle: Stay in each phase long enough. Rushing to "Run" creates gaps.

爬：你们一起评审PR，边操作边讲解你关注的要点、背后的原因，以及代码优劣的判断标准。

走：由他们进行评审，你在旁观察。通过提问引导：“这部分你怎么看？”实时纠正偏差。

跑：他们独立完成评审。你偶尔抽查，并讨论出现的分歧。遇到边缘案例时他们会主动向你请教。

核心原则：在每个阶段停留足够长的时间。急于进入“跑”阶段会导致知识漏洞。

Socratic Questioning

苏格拉底式提问法

Instead of giving answers, ask questions that lead to understanding:

Instead of...	Ask...
"Use a hash map here"	"What data structure would give us O(1) lookups?"
"You need to handle null"	"What happens if this value is null?"
"That's inefficient"	"What's the time complexity here? Could we do better?"
"Don't do it that way"	"What are the trade-offs of this approach?"

不直接给出答案，而是通过提问引导学员自主理解：

不要说...	可以问...
“这里用哈希表”	“哪种数据结构能实现O(1)时间复杂度的查找？”
“你需要处理空值情况”	“如果这个值是空的会发生什么？”
“这种方式效率很低”	“这个方案的时间复杂度是多少？我们能优化吗？”
“不要这么做”	“这种方案的优缺点是什么？”

Benefits

优势

They learn to think, not just memorize
Builds problem-solving muscles
They discover answers themselves (more memorable)
You understand their thought process

When NOT to use Socratic questioning:

Production incident - just tell them the fix
Simple factual questions - don't make them guess
When they're frustrated or overwhelmed

培养学员的思考能力，而非单纯记忆
锻炼解决问题的能力
学员自主发现答案（记忆更深刻）
你能了解学员的思考逻辑

何时不使用苏格拉底式提问法：

生产事故发生时——直接告知解决方案
简单的事实性问题——不要让对方猜测
学员感到沮丧或压力过大时

Building Trust

建立信任

Trust is the foundation of effective mentoring:

信任是高效指导的基础：

Trust-Building Practices

信任构建方法

Show genuine interest in their goals
- Ask about career aspirations
- Remember and follow up on personal details
- Celebrate their wins publicly
Create psychological safety
- Normalize mistakes: "I make these too"
- Share your own failures and learnings
- Never shame, even privately
Maintain confidentiality
- What they share stays between you
- Don't mention their struggles to others
- Ask before sharing their work as examples
Be consistent and reliable
- Show up to 1:1s on time
- Follow through on commitments
- Be honest about your own limitations
Acknowledge when they teach you
- Mentoring is bidirectional
- Let them know when you learned from them
- Builds their confidence and equalizes the relationship

真正关注学员的目标
- 询问职业抱负
- 记住并跟进学员的个人情况
- 公开庆祝他们的成就
营造心理安全感
- 正常化错误：“我也犯过这些错”
- 分享你自己的失败经历和经验教训
- 即使私下也不要羞辱学员
保持保密性
- 学员分享的内容仅限你们双方知晓
- 不要向他人提及学员的困境
- 引用学员的工作作为案例前需征得同意
保持始终如一与可靠
- 准时参加一对一会议
- 兑现承诺
- 坦诚承认自己的局限性
认可学员的教学价值
- 指导是双向的
- 让学员知道你从他们身上学到了什么
- 增强他们的信心，让关系更平等

Tailoring to Learning Styles

适配学习风格

People learn differently. Adapt your approach:

Style	Signs	Approach
Visual	Asks for diagrams, draws things out	Use whiteboarding, architecture diagrams, code walkthroughs
Auditory	Learns from discussion, podcasts	Talk through concepts, think-aloud, verbal explanations
Kinesthetic	Prefers hands-on practice	Pair programming, experiments, building things
Reading/Writing	Prefers documentation	Point to docs, have them write summaries

Most people are a mix. Start with all approaches, then observe what clicks.

不同人的学习方式不同。调整你的指导方法：

学习风格	特征	指导方法
视觉型	要求提供图表，喜欢画图	使用白板、架构图、代码走查
听觉型	从讨论、播客中学习	讲解概念、边操作边思考、口头解释
动觉型	偏好动手实践	结对编程、实验、实际搭建项目
读写型	偏好文档资料	指向相关文档，让他们撰写总结

大多数人是混合型。先尝试所有方法，再观察哪种最有效。

Pair Programming for Mentoring

用于指导的结对编程

Pair programming is a powerful mentoring tool when done well. See

references/pair-programming-guide.md

for detailed guidance.

结对编程是一种强大的指导工具，前提是方法得当。详细指导请参阅

references/pair-programming-guide.md

。

Key Principles

核心原则

Rotate driver/navigator roles
Narrate your thinking when driving
Let them struggle (productively)
Never grab the keyboard without permission

轮换驾驶员/导航员角色
当你作为驾驶员时，说出你的思考过程
让学员适度尝试（有效试错）
未经允许不要直接操作键盘

1:1 Meeting Structure

一对一会议结构

Effective 1:1s are the backbone of mentoring. See

references/one-on-one-structure.md

for detailed templates.

高效的一对一会议是指导工作的支柱。详细模板请参阅

references/one-on-one-structure.md

。

Basic Structure (30 min)

基础结构（30分钟）

Progress check (5 min)
Challenges/blockers (10 min)
Development goals (10 min)
Open discussion (5 min)

进度检查（5分钟）
挑战/障碍（10分钟）
发展目标（10分钟）
开放式讨论（5分钟）

Key Principles for 1:1s

一对一会议核心原则

Their agenda, not yours
Consistent cadence (weekly ideal)
Take notes and follow up
Occasionally skip status and go deep on growth

以学员的议程为主，而非你的
保持固定频率（理想为每周一次）
做好记录并跟进
偶尔跳过状态汇报，深入探讨成长话题

Common Mentoring Mistakes

常见的指导误区

Taking Over

过度主导

❌ Grabbing the keyboard when they struggle ✅ Ask guiding questions, let them try

❌ 学员遇到困难时直接接管操作 ✅ 提出引导性问题，让他们自己尝试

Assuming Knowledge

预设已有知识

❌ "You know what a REST API is, right?" ✅ "What's your experience with REST APIs?"

❌ “你知道什么是REST API吧？” ✅ “你有使用REST API的经验吗？”

Overwhelming with Information

信息过载

❌ Explaining everything about microservices at once ✅ Focus on what they need now, save rest for later

❌ 一次性讲解微服务的所有内容 ✅ 聚焦学员当前需要的知识，其余内容延后讲解

Neglecting the Relationship

忽视关系维护

❌ Only discussing technical work ✅ Check in on how they're doing personally

❌ 仅讨论技术工作 ✅ 关心学员的个人状态

Doing vs. Teaching

代替操作而非教学

❌ "I'll just fix this, it's faster" ✅ "Let's fix this together so you see how"

❌ “我来修吧，这样更快” ✅ “我们一起修复，让你了解过程”

Measuring Progress

进度衡量

Track mentee development over time:

长期跟踪学员的发展情况：

Technical Progress

技术进度

PRs requiring less revision
Taking on more complex tasks
Helping others with areas you taught

PR需要的修改次数减少
承担更复杂的任务
能够帮助他人解决你教过的领域的问题

Professional Progress

职业发展

More confident in meetings
Asking better questions
Navigating team dynamics effectively

在会议中更自信
提出更有质量的问题
能有效应对团队动态

Relationship Health

关系健康度

They bring you problems early
Honest about struggles
Proactive about scheduling time

学员会提前向你反馈问题
坦诚分享自己的困境
主动预约指导时间

Related Resources

Version History

版本历史

v1.0.0 (2025-12-26): Initial release

v1.0.0（2025-12-26）：初始版本

Last Updated

最后更新

Date: 2025-12-26 Model: claude-opus-4-5-20251101

日期： 2025-12-26 模型： claude-opus-4-5-20251101