The way we teach tech
summary
Argues teaching must be concrete and iterative: start with make it work make it good make it fast, use a real bug (logging example) to teach env vars, dependency injection, interfaces and decorators step by step. Emphasizes context-sensitive help (solve → understand → choose), promotes use juniors in code review and pair programming as teaching tools, recommends event storming, meetups and small controlled experiments. Claims the workforce skews junior (programmers double every five years).
AI-written summary · about
chapters (13)
- 0:00Start
- 1:05We are hiring!
- 10:33stackoverflow
- 17:18I want to log errors
- 19:51Code Review
- 25:45Why Dependency Injection is good
- 27:03Online Courses
- 27:19Pair Programming
- 28:36Meetups
- 29:22The Pac-Man Rule
- 29:58EventStorming
- 32:53Small Controlled Experiments
- 34:54Absolutes
related talks
30mLessons Learned: A Developer's Perspective on Teaching & Learning
45mTeach by Learning; Lead by Teaching
01h 06mTeaching New Tricks – How to enhance the skills of experienced developers
36mTeach Your Way To Better Code
31mDEAR JUNIOR DEVELOPER ME
02h 05mWhy We’re Teaching Programming Wrong: A Haskell Perspective
08mThe Noobs and the Programmers: On Teaching Programming
34mThose Who Can Do Should Also Teach