GlobeRead Teach Yourself Programming in Ten Years — GlobeRead
Personal Development Self Education Technology

Teach Yourself Programming in Ten Years

By Peter Norvig ·www.norvig.com

Peter Norvig's now-canonical essay — available since the early 2000s and updated periodically — reacting to the ''Teach Yourself Java in 24 Hours'' genre of programming books. Drawing on Bloom's research and Anders Ericsson's work on deliberate practice, Norvig argues that real programming expertise takes ten years of deliberate practice, not 21 days. Includes a practical recipe: get interested, program a lot with feedback, work with experienced programmers, work after other programmers, learn multiple paradigms, and understand the hardware.

Read full article at www.norvig.com →

Opens on www.norvig.com · Curated by GlobeRead

GlobeRead's Take

The ''teach yourself X in 24 hours'' publishing genre has been running for thirty years and shows no sign of collapsing, which tells you something important about what people want from learning materials versus what actually produces skill. Norvig's essay has been circulated in developer communities since the early 2000s as a kind of antidote — a two-page reality check from Google's then-Director of Research, who spent decades inside both academia and industry watching how people actually learn to program.nnThe first and most useful move is the citation of Ericsson's research. Bloom's 1985 study of top performers and Bryan & Harter's 1899 work on telegraph operators independently arrived at the same conclusion: the highest performance levels in any complex domain require roughly ten years of deliberate, effortful practice — not practice in the sense of repetition, but practice in the sense of challenging yourself at the edge of your current ability, receiving feedback, and correcting mistakes. Gladwell later popularised the 10,000-hour version of this. Norvig's point is that no programming book can compress this down; the book can at best get you started.nnThe second move is the practical recipe, which is unusually specific for this genre. Norvig recommends: programming for fun first, because sustained effort requires intrinsic motivation; talking with experienced programmers rather than reading about them; working on projects after other programmers, because reading someone else's code and fixing it teaches more than starting fresh; learning at least six programming languages across different paradigms; and understanding what the hardware is actually doing, not just what the language abstraction tells you. Most introductory advice ignores the last two entirely.nnWe picked this because it is one of the few pieces of career advice for programmers grounded in actual cognitive science rather than anecdote — useful for anyone starting to program and anyone who has been programming for five years and wonders why they still feel like a beginner. The uncomfortable question is whether your current practice is genuinely deliberate or merely repetitive.



Found this on GlobeRead?
We curate the internet's most interesting articles — science, psychology, history, philosophy and more. Always free, no algorithm.
Explore all articles →