Working Together: Pairing as Senior and Junior Developers
summary
Argues that concrete habits beat vague promises: give a one-line summary of what should happen, list what is happening, and summarize problem and desired outcome; include context, story card and provide links to relevant files or a pushed PR; prepare test data and servers; use Rails console, browser devtools network tab, logs, binding.pry and other debugging tools; use conditional “we” language, ask guiding questions, and after pairing state one thing learned. A study shows 70% of professional learning is informal.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:32Rationale for Presentation
- 5:29Before Pairing
- 8:06Poorly-Structured Questions
- 11:19Be Prepared
- 14:46Ask Questions and Make Suggestions
- 18:06Provide Debugging Tools
- 19:53Reflection
- 21:34Major Takeaways
related talks
26mHow to be an Awesome Junior Developer
13mGrowing Developers: Helping Junior Developers Improve & Succeed
37mPairing with Intention: A Guide for Mentors
30mEquipping your team to support junior developers
46mGrowing a Junior Dev into a Beautiful Coding Butterfly
37mPairing with Intention: A Guide for Mentors
36mTeach Your Way To Better Code
33mCoaching through Coding