Self‑taught, is that a problem doctor?
summary
The talk examines self-taught software developers, questioning whether their situation is a problem that needs ‘fixing’ or simply a difference to accept. It discusses understanding different learning paths and challenges common assumptions about how developers should learn, using a playful, provocative approach.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:08Self-taught proportion in dev
- 2:34Autodidacty definition
- 6:53Practice-based learning in schools
- 8:02Recognizing autodidacts
- 11:12Impostor syndrome and bias
- 14:26Ending discrimination
- 15:30Studies or not?
- 16:16Conclusion
- 18:06Finding good sources
- 20:35Learning the unknown
- 26:56Tools and monitoring for autodidacts
- 27:17Autodidacty vs studies
- 30:03Must all devs be self-taught?
- 31:50Solo vs team coding
- 35:49Non-engineer profiles
- 38:41Conclusion and call
related talks
45mTeach by Learning; Lead by Teaching
56mLearning to Teach Programming
45mLearning to Learn Better
31mRethinking How We Teach Web Development
46mDeveloping Your Developers’ Development: How Learning Can Have Impact and Why It Sometimes Doesn’t
51mYour worth as a developer: not what you do, but why
55mWhen will you learn? A Teacher’s Guide to Developer Learning
36mSharpening The Axe: Self-Teaching For Developers