You Can Be a Mentor for the Next Cohort of Android Engineers
summary
Argues that engineers at any level can run practical mentorship by building peer mentoring routines like weekly study groups to migrate a codebase to Compose, pairing on Kotlin coroutines and teaching unit tests for coroutines, or running brown‑bag demos on Retrofit→Kotlin transitions. Gives measurable outcomes to track—juniors shipping tests with every PR and test coverage rising, reduced senior bottlenecks, faster Compose rollout—and warns about unpaid glue work risk while advising to log impact to managers.
AI-written summary · about
chapters (8)
- 0:00Introduction to mentoring
- 5:27Why mentoring skills matter
- 8:39Redefining mentorship
- 12:54Finding knowledge gaps
- 17:54Risks of glue work
- 22:52Measuring mentoring impact
- 27:02Mentoring beyond the team
- 29:50Q&A and resources
related talks
46mBecoming a mentor, why and how?
21mThe Critical Need for More Android Mentors
34mSupporting Each Other: Growth for Juniors and Seniors
34mSupporting Each Other: Growth for Juniors and Seniors
50mEmpathic Mentoring for Developers - Why Should You Care, and How?
35mBecoming a mentor, why and how?
35mYou Should Mentor That Person
26mMentorship programs. Growing new team and community leaders