How to Train Your Dragon
summary
Engineering teams create juniors fast but fail to grow them; claim backed by 16 recorded interviews across bootcamps, universities, recruiters and HR. Practical fixes: document major product and code decisions, publish pedantic daily routines (pull main, rebase, PR templates), assign clear team roles, run one-on-one goal checklists and pair programming sessions. Warns that unfettered AI/codegen hides learning — a Replets-generated multiplayer crypto app runs but contains a single-websocket bug so only one player actually functions.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 4:20The mentorship gap in engineering
- 7:51Tools and teamwork for juniors
- 13:02Clear guidelines and daily routines
- 16:30Business absurdity and documentation
- 21:08Constraints and creativity in coding
- 23:15AI's impact on junior engineers
- 27:11Takeaways and call to action
related talks
22mJunior Engineers Are Features, Not Bugs
30mEquipping your team to support junior developers
31mHurdles of Junior Developers and How To Overcome Them
33mJunior Engineers Are Features, Not Bugs
35m10 Lessons for Growing Junior Developers
37mDungeons, Dragons & Developers
27mEngineering in the Age of AI: Making AI Work for Us, Not Replace Us
17mManaging the Gap AI Brings: Keeping Developers Sharp and Engaged