Azurelunatic (talk | contribs) (→Mistakes to avoid in mentoring: pre-existing hate is not conducive to anybody learning anything) Tags: Visual edit apiedit |
Azurelunatic (talk | contribs) (mistakes: you are not a godlike being with perfect knowledge of the subject) Tags: Visual edit apiedit |
||
| Line 27: | Line 27: | ||
** It may be a struggle for them to do something that the mentor could whip out in five minutes, but depriving the learner of the opportunity to struggle through and make mistakes will hold them back from learning it effectively. |
** It may be a struggle for them to do something that the mentor could whip out in five minutes, but depriving the learner of the opportunity to struggle through and make mistakes will hold them back from learning it effectively. |
||
* Never get into a mentorship relationship with someone you hate, or who hates you. |
* Never get into a mentorship relationship with someone you hate, or who hates you. |
||
| + | * You don't have to know everything. |
||
| + | ** Don't be afraid to admit when you're not sure. |
||
| + | ** Don't be afraid to look things up. |
||
| + | ** Be open to the idea that your learner may know some things that you don't. |
||
Revision as of 22:20, 19 April 2015
A mentor is a more experienced person who offers advice, support, and professional development to a more junior person.
Lack of women mentors has been identified as a problem for women in the technology industry and other geek fields.
There are some mentoring programs aimed at women in geek fields, including:
- Empowermentors
- Women Entering and Staying in Tech (WEST)
- TechWomen Mentors
- ARA (Attract, Retain, Advance)
- ...
How to be an effective mentor
- Critique the code, not the programmer.
- Point out specific problems which can be fixed.
- Make sure you're on the same page; don't assume that silence means they're with you and paying attention.
- Make sure you're on the same page; they may already be very familiar with the thing you're explaining.
- Be aware of your organization's history. Why was a specific decision made? What are the factors which went into that decision? What has changed since that time?
- You may discover a number of things which need documenting. Creating the documentation together may be a great way to make sure the learner has grasped the topic.
Mistakes to avoid in mentoring
- Don't do this: XKCD: Code Quality
- Unless you have a very trusted and close relationship where that sort of thing is okay, try not making fun of someone who doesn't know things.
- Don't insult the person who is learning from you.
- Don't assume that just because something has "always" been done that way, that it's the best way or that it can't be changed.
- Avoid the temptation to just do it for the learner.
- It may be a struggle for them to do something that the mentor could whip out in five minutes, but depriving the learner of the opportunity to struggle through and make mistakes will hold them back from learning it effectively.
- Never get into a mentorship relationship with someone you hate, or who hates you.
- You don't have to know everything.
- Don't be afraid to admit when you're not sure.
- Don't be afraid to look things up.
- Be open to the idea that your learner may know some things that you don't.