Quit Frustrating Your New Developers - Tips From a Teacher
summary
Practical steps and measurable signals decide whether to watch: a six to eight weeks onboarding plan, a written New Engineer's Handbook that covers machine setup and expectations, a Slack onboarding channel for private questions, and using PRs and style‑guide reviews for regular feedback. Claims: training must reduce unknowns and teach problem‑solving, psychological safety (Google study) matters, and counting interactions (40 vs 200) predicts comfort asking questions. Examples and numbers are explicit; tools and outcomes are concrete.
AI-written summary · about
chapters (22)
- 0:00Quit Frustrating Your New Developers - Tips From a Teacher
- 1:56EXPOSING MY PREFERENCES
- 2:58TEACHING OPPORTUNITIES
- 3:33TYPES OF KNOWLEDGE
- 4:54OVERVIEW OF TEACHING/TRAINING
- 8:00SELF ASSESSMENT QUESTIONS
- 9:48THE SEVEN LAWS OF TEACHING
- 10:15THE LAW OF THE TEACHER
- 10:32ONBOARDING
- 13:34CONTINUING EDUCATION / MENTORING
- 15:52ROUTINE QUESTIONS
- 16:22THE LAW OF THE LEARNER
- 18:52OPPORTUNITIES FOR INTERACTIONS
- 20:41THE LAW OF THE LANGUAGE
- 20:552 KEYS TO SUCCESS
- 22:28THE LAW OF THE LESSON
- 26:01THE LAW OF THE TEACHING PROCESS
- 26:57BENEFITS TO JUST ANSWERING A QUESTIONS
- 29:09QUESTION AND ANSWER FLOW
- 30:24THE LAW OF THE LEARNING PROCESS
- 32:27THE LAW OF REVIEW AND APPLICATION
- 33:39THE FIVE KEYS TO A SUCCESSFUL GOOGLE TEAM
related talks
06mEffective Onboarding: From Zero to Full Speed
30mTechnical Onboarding, Training, and Mentoring
21mHow to quickly get engineers up to speed
34mDeep End Diving: Getting Up to Speed on New Codebases
28mDesigning for Success: UX Principles for Internal Developer Platforms
35mBuilding Effective Developer Experience
52mSpeeding Developer Onboarding: Practical Lessons
30mEquipping your team to support junior developers