To someone new, IMO a mentors primary jobs are:
1. Be there.
2. Be welcoming.
3. Be patient.
4. Make sure they're recognized.
5. Be a DNS server. They don't know to go or who to ask, you'll be asked for a "who...?" a lot. Documentation helps, but is rarely 100%.
#DevDiscuss
1. Be there.
2. Be welcoming.
3. Be patient.
4. Make sure they're recognized.
5. Be a DNS server. They don't know to go or who to ask, you'll be asked for a "who...?" a lot. Documentation helps, but is rarely 100%.
#DevDiscuss
Mentoring comes first.
Your work comes second.
Ideally, pair on things to do both.
YOU NEED THE BACKING OF MANAGEMENT/PM/ETC. ON THIS.
The last part is critical. It's a marathon and you're supposed to be investing. Don't sacrifice tomorrow to ship something today.
#DevDiscuss
Your work comes second.
Ideally, pair on things to do both.
YOU NEED THE BACKING OF MANAGEMENT/PM/ETC. ON THIS.
The last part is critical. It's a marathon and you're supposed to be investing. Don't sacrifice tomorrow to ship something today.
#DevDiscuss
Mentoring cannot be an afterthought or something "on the side". It has to be a primary function and a priority. It's not fair to either side if it's anything less.
The org needs to make it a priority if they're serious about it. And if they do, it'll pay dividends.
#DevDiscuss
The org needs to make it a priority if they're serious about it. And if they do, it'll pay dividends.
#DevDiscuss
These are my observations from friends, colleagues, new devs here and elsewhere, and seeing most of them grow (and some not).
I consider myself a terrible mentor because I never have enough time to do it well. Advice on the fly is as good as time allows the last few years.
I consider myself a terrible mentor because I never have enough time to do it well. Advice on the fly is as good as time allows the last few years.
