Amazing internships!
summary
Uses a 13-week model with a 10-week main project that must be deployable to someone outside the team, allocates week one for onboarding and the last week for review, and reserves launch time to collect real user feedback; insists on up‑to‑date docs, small integrated exercises and a safe test environment for experiments, and requires a backup host so progress survives illness or travel — interns repeatedly deliver working, reviewable features.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:50What Makes an Internship Successful
- 2:55Be Respectful
- 3:39Planning
- 10:48Backup Host
- 11:33Checklist
related talks
10mMaking your interns succeed!
25mAgile Development with Interns
17mAre Your Interns Actually Sad? The Answer May...
27mSustainability Starts Early: Creating a Great Ops Internship
31mInternships: Good for the Intern, Great for the Team
26mThe Intern Effect
01h 12mStart a Ruby Internship
32mFrom Classroom To Cloud: Bridging Academia and the Open Sou...