Panel: Teaching the Next Great Developers
summary
Panelists from DevBootcamp Chicago Jumpstart Labs Turing Thoughtbot and Girl Develop It describe concrete outcomes: students learn how to learn, get nine‑week immersive tracks (Rails introduced in week seven), do three‑week team projects and daily TDD starting on day two, and instructors run pair‑programming, mentoring and take‑home coding assignments. Hiring favors in‑person pairing over whiteboard puzzles; apprenticeships yield junior hires who deliver like one to two years of experience. Expect 80–90 hour weeks and explicit engineering‑empathy coaching.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 7:30What we teach
- 8:40My experience
- 10:05Youre not terrible
- 10:40Imposter syndrome
- 15:10What does great mean
- 15:55Programming is a force multiplier
- 17:35Im here for you
- 18:40Engineering Empathy
- 20:40Fostering Interpersonal Communication
- 23:40Demand vs Supply
- 24:25The Incoming Side
- 25:30Apprenticeships
- 26:15The best immediate juniors
- 27:10Learning time
- 29:20Reassess goals
- 30:45TDD
- 32:05Interview Process
- 34:00Interview Experience
- 34:50Interview Pairing
- 35:30Thought Works
- 36:30A World of Difference
- 37:15Do you want to be a professional developer
- 37:50Bootcamps
- 39:30Outro
related talks
35m10 Lessons for Growing Junior Developers
33mThe Pivotal Engineering Dojo
38mGrow Your Team In 90 Days
01h 35mSoftware Teaming [Mob Programming] mini-workshop
40mCraft: From Concepts to Large-Scale Deployment
34mThose Who Can Do Should Also Teach
37mLearning technical practices using mob programming
35mClosing Keynote
