Mentoring technical practices, what works and not
summary
Describes a five-year mentoring program that uses pairing, weekly exercises derived from the production repo and one-day workshops to teach refactoring and tests; a 500-line method becomes 500 lines to 4 lines by applying LINQ and small refactor steps, 20 people attend a code-retreat with code retreat 25/5 rounds, and a Ruby on Rails sandbox spurs ideas that cut deployment time to less than 30 minutes. Outcomes: participants gain confidence to change code, add tests, and adopt ReSharper hotkeys; prerequisite 3 hours 1:1 mentoring for advanced workshops.
AI-written summary · about
chapters (10)
- 0:00Start
- 12:22TDD workshop followed by pairing with team members for two weeks
- 15:37Community Mini-Coderetreat
- 17:43Refactoring Kata
- 19:55One-on-one Mentoring
- 25:252-week Mentoring with Senior Developers
- 28:16Four Stages of Competence
- 35:45What improvements to the course do you suggest?
- 36:50What aspects of the course were most successful in helping you to learn?
- 38:29Assignments as a Pre-requisite
related talks
38mTechnical Coaching
34mDeep End Diving: Getting Up to Speed on New Codebases
26mMentorship programs. Growing new team and community leaders
42mGetting Ahead By Deleting Code
37mLearning technical practices using mob programming
39mLocal Community Building
33mTapping into the power of junior developers
01h 15mKeynote: Technical Agile Coaching With the Samman Method