Supporting Each Other: Growth for Juniors and Seniors
summary
Argues that hiring juniors pays off despite onboarding cost, citing six Android developers who came and went in one first year as evidence of turnover pressure; juniors bring fresh motivation and knowledge (example: MotionLayout), plus a flexible mindset. Recommends concrete practices: sketch architecture, follow MVVM/repository/use‑case layers with Dagger and Rx, use pair programming, keep criticism private and praise public, give varied tasks, and apply a 4 hours timebox/rubber‑duck routine before asking for help. Mentoring grows seniors too.
AI-written summary · about
chapters (17)
- 0:00Introduction and welcome
- 1:05Why hire junior developers
- 5:20Where do seniors come from
- 7:50Imposter syndrome in juniors
- 9:12Benefits juniors bring to teams
- 12:02Manager expectations for juniors and seniors
- 14:56What seniors gain from mentoring
- 16:01What mentoring really means
- 19:13Effective communication with juniors
- 20:20Sketching ideas to simplify explanations
- 22:26Constructive code reviews and feedback
- 23:51Assigning appropriate tasks to juniors
- 24:32Creating a supportive team environment
- 25:18Pair programming for growth
- 25:40Tips for junior developers
- 31:41Overcoming doubts about hiring juniors
- 33:04Closing and Q&A invitation
related talks
34mSupporting Each Other: Growth for Juniors and Seniors
36mSupporting Each Other: Growth for Juniors and Seniors
14mJunior.next()
31mFostering a Welcoming, Supporting Productive Environment for Junior Developers...
45mHiring Juniors
25mProper Care and Feeding of Junior Developers
46mBecoming a mentor, why and how?
30mYou Can Be a Mentor for the Next Cohort of Android Engineers