Coaching through Coding
summary
Argues that senior engineers coach through everyday work by pairing, PRs, debugging, estimates and docs, not just formal mentorship. Recommends 50 percent driving time during pair sessions and using driver/navigator swaps to teach debugging discipline. Suggests PRs include rationale and links so reviews become living docs, cites an Oracle adapter performance PR where in-line comments explained tradeoffs. Advises researching libraries by inspecting their source and tests — check library test suites — and to link PRs to docs so knowledge is discoverable.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:28Coaching through coding
- 5:03The 10x developer
- 6:21Mentorship vs. Coaching
- 8:21Pair programming
- 8:45Navigating
- 11:16Driving
- 14:41Debugging
- 17:08Code reviews
- 23:49No-code technical tasks
- 23:59Estimating
- 26:38Architecture diagrams
- 30:57Share joy in learning
related talks
35mBecoming a mentor, why and how?
53mHow to really work together as a team
36mTeach Your Way To Better Code
23mWorking Together: Pairing as Senior and Junior Developers
14mThe Tech Coach strikes back
30mLessons Learned: A Developer's Perspective on Teaching & Learning
37mPairing with Intention: A Guide for Mentors
01h 04mCoder, Coach, Catalyst - using questions to make people grow