Internships: Good for the Intern, Great for the Team
summary
Recommend hiring interns who pair for six weeks, then do a month‑long solo project, then pair again; assign a mentor and schedule daily mentor check-ins. Expect to find concrete bugs in onboarding, confusing model names, and teaching gaps; run code review and let interns type. Typical team can support one intern with 1–2 seniors, 1–2 mid‑level devs, and 1–2 juniors. Pay interns legally; internships surface auditable problems and can measurably improve diversity and retention.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:11True Stories
- 6:453 THE CUTTING-EDGE CAT
- 7:28AUDITS, ALL
- 8:17Structure Matters
- 10:31MAKE THE BUSINESS CASE
- 11:37HAVE GOALS
- 12:54TEAM COMPOSITION
- 13:36PAIRING
- 16:39YOU WILL LEARN SAD THINGS
- 19:29THE SOLO PROJECT
- 20:14PICKING A PROJECT
- 20:52CODE REVIEW
- 22:05MENTORSHIP
- 23:13CONSULTANCY? HMMM.
- 26:33HOW TO DIVERSITY
- 27:22RECRUITING AND INTERVIEWING INTERNS
- 29:01Things I'd Change
- 30:13Audits are helpful!
