Junior Engineers Are Features, Not Bugs
summary
Claims that hiring juniors forces fixes in three areas—architecture, process, tooling—are backed by examples: a team with one third code‑school grads runs ~85% of web/API traffic; a principal’s hand‑drawn service map becomes a small web app; an undocumented SAML API gets decoded with Wireshark; an 18‑step deploy becomes automated plus checklists; backup/restore gets weekly tests; a two‑person apprentice program converts after six months; hiring for scrappiness, self‑reflection, and an onboarding buddy village shows measurable improvement in resilience.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:35What the #®*$ do I know?!
- 3:51Terminology
- 4:33Sources
- 5:38Setting the scene
- 8:06Architecture
- 9:23Process
- 10:08Tooling
- 12:10Antipatterns
- 13:15Better Practices
- 14:25Benefits of Junior Engineers
- 16:00Potential
- 21:46Superpowers
- 23:56Onboarding Buddy Village
- 27:51Managing Expectations
- 28:33Summary
- 30:04Our Points of Failure
- 32:00Challenge
related talks
22mJunior Engineers Are Features, Not Bugs
45mHiring Juniors
19mFrom Junior Engineer to Productive Engineer
31mFostering a Welcoming, Supporting Productive Environment for Junior Developers...
32mThe Fake Problem with Junior Developers
23mSuccessfully Onboarding a Junior Engineer in Three Steps
46m"Junior" Devs are the Solution to Many of Your Problems
35m10 Lessons for Growing Junior Developers