When will you learn? A Teacher’s Guide to Developer Learning
summary
Five concrete practices for ongoing developer growth: create your own curriculum that schedules brief practice, reflection and peer feedback; use specific tools like Codecademy, FreeCodeCamp, Stack Overflow, meetups and open‑source contributions; apply the four R checklist—resourcefulness, reflectiveness, reciprocity, resilience—after each learning sprint; mentor and review code peer‑to‑peer instead of top‑down; measure impact: contributors report ~80% higher learning gains and community members can earn ~15% more. A classroom water‑transport project shows meta‑reflection immediately improves results.
AI-written summary · about
chapters (9)
- 0:00Welcome
- 3:37Myth of staying relevant
- 10:16Why developers struggle
- 22:55Building your curriculum
- 31:02Love of learning and failure
- 40:42Tech communities for growth
- 48:49Peer-to-peer learning
- 56:26Myth of the savant
- 1:00:21Final thoughts and Q&A
related talks
55mWhen will you learn? A Teacher’s Guide to Developer Learning
30mLessons Learned: A Developer's Perspective on Teaching & Learning
29mActive Learner - How developers keep learning
35mSharpening The Axe: Self-Teaching For Developers
31mBuilding good developers
36mSharpening The Axe: Self-Teaching For Developers
27mWhen the teacher becomes a student: an honest guide to becoming a developer
15mLearning Tips Every Developer Should Know