Becoming a mentor, why and how?
summary
Android mentoring focuses on concrete practices not platitudes: use pair programming (screen share or Code With Me) as the primary tool, schedule regular pairing blocks, and timebox tasks to 2–3 hours so juniors don’t stall for days. Teach four measurable growth areas — solving, communication, organization, presenting — enforce PR hygiene (self-review, comment with suggested fixes, keep changes reasonable not one giant 600+ line dump) and give immediate corrective and celebratory feedback.
AI-written summary · about
chapters (18)
- 0:00Intro
- 6:00Who am I
- 6:12What is Trade Republic
- 6:57What is mentoring
- 8:18Why mentor
- 10:34Main issue
- 10:45First catch up
- 13:56First tasks
- 15:15Regular process
- 15:36Pairing
- 18:10Areas of growth
- 19:34Solving skills
- 24:30Soft skills
- 27:27Organizational skills
- 32:15Presentation skills
- 36:02Feedback
- 39:41Conclusion
- 41:50Advice
related talks
35mBecoming a mentor, why and how?
30mYou Can Be a Mentor for the Next Cohort of Android Engineers
21mThe Critical Need for More Android Mentors
34mSupporting Each Other: Growth for Juniors and Seniors
24mHow to be a good mentor
33mMentoring, For me or not for me, that is the question
21mMeaningful Mentorship for Developers
55mMentorship Panel