How to be an Awesome Junior Developer
summary
Describes hiring and mentoring practices with concrete examples: a rescue Rails app stores ~100 attributes in a single text field called data, leading to two to three weeks of wrote tests for legacy models to document and protect behavior before changing it; recommends a pull-request-only policy and half-day pairing in interviews; contrasts bad vs Socratic code review (teaches use of Rails try instead of nil checks); recounts building a real-time World Cup API in days (JSON + Rabl), which hit GitHub trending with ~300 stars.
AI-written summary · about
chapters (16)
- 0:00Intro
- 2:07Who am I
- 2:52Why I started coding
- 5:13Getting hired
- 7:45My first day
- 9:46Schema
- 11:34Mentoring
- 13:01Code Review
- 14:04Bad vs Good Code Review
- 16:38Code Reviews
- 17:27Side Project
- 20:49Lessons Learned
- 21:29Time Zones
- 22:13Design Patterns
- 22:57Watching Other People Code
- 23:44The Pipeline
related talks
13mGrowing Developers: Helping Junior Developers Improve & Succeed
23mWorking Together: Pairing as Senior and Junior Developers
39mNew Dev, Old Codebase: A Series of Mentorship Stories
31mHurdles of Junior Developers and How To Overcome Them
36mHow to be a Better Junior Developer
29mHacking Development Culture: Treating Developers As People
01h 05mLegacy Rails Q&A
22mJunior Gems: Hiring, Valuing, and Empowering the Next Wave of Ruby Developers