Teach Yourself Programming in Ten Years
Peter Norvig
Why is everyone in such a rush?
Walk into any bookstore, and you'll see how to
Teach Yourself Java
in 7 Days alongside endless variations offering to teach Visual
Basic, Windows, the Internet, and so on in a few days or hours. I did
the following at :
and got back 248 hits. The first 78 were computer books (number 79
was ). I replaced "days" with
and got remarkably similar results: 253 more books, with 77 computer
books followed by at number 78. Out of
the top 200 total, 96% were computer books.
The conclusion is that either people are in a big rush to learn
about computers, or that computers are somehow fabulously easier to
learn than anything else. There are no books on how to learn
Beethoven, or Quantum Physics, or even Dog Grooming in a few days.
Felleisen et al.
give a nod to this trend in their book , when they say
"Bad programming is easy. Idiots can learn it in 21 days,
even if they are dummies.
Let's analyze what a title like
could mean:
- Learn: In 3 days you won't have time to write several
significant programs, and learn from your successes and failures with
them. You won't have time to work with an experienced programmer and
understand what it is like to live in a C++ environment. In short, you
won't have time to learn much. So the book can only be talking about a
superficial familiarity, not a deep understanding. As Alexander Pope said,
a little learning is a dangerous thing.
- C++: In 3 days you might be able to learn some of the syntax of
C++ (if you already know another language), but you couldn't
learn much about how to use the language. In short, if you were, say, a
Basic programmer, you could learn to write programs in the style of
Basic using C++ syntax, but you couldn't learn what C++ is
actually good (and bad) for. So what's the point? once said: "A language that doesn't affect the way you
think about programming, is not worth knowing". One possible point is
that you have to learn a tiny bit of C++ (or more likely, something
like JavaScript or Flash's Flex) because you need to interface with an
existing tool to accomplish a specific task. But then you're not
learning how to program; you're learning to accomplish that task.
- in Three Days: Unfortunately, this is not enough, as the next
section shows.
Teach Yourself Programming in Ten Years
Researchers (, , , ) have shown it
takes about ten years to develop expertise in any of a wide variety of
areas, including chess playing, music composition, telegraph
operation, painting, piano playing, swimming, tennis, and research in
neuropsychology and topology. The key is
deliberative
practice: not just doing it again and again, but challenging yourself
with a task that is just beyond your current ability, trying it,
analyzing your performance while and after doing it, and correcting
any mistakes. Then repeat. And repeat again. There appear to be no
real shortcuts: even Mozart, who was a musical prodigy at age 4, took
13 more years before he began to produce world-class music. In
another genre, the Beatles seemed to burst onto the scene with a
string of #1 hits and an appearance on the Ed Sullivan show in 1964.
But they had been playing small clubs in Liverpool and Hamburg since
1957, and while they had mass appeal early on, their first great
critical success,
Sgt. Peppers, was released in 1967.
reports that a study of students at the Berlin Academy of
Music compared the top, middle, and bottom third of the class and
asked them how much they had practiced:
Everyone, from all three groups, started playing at roughly the same
time - around the age of five. In those first few years, everyone
practised roughly the same amount - about two or three hours a
week. But around the age of eight real differences started to
emerge. The students who would end up as the best in their class began
to practise more than everyone else: six hours a week by age nine,
eight by age 12, 16 a week by age 14, and up and up, until by the age
of 20 they were practising well over 30 hours a week. By the age of
20, the elite performers had all totalled 10,000 hours of practice
over the course of their lives. The merely good students had totalled,
by contrast, 8,000 hours, and the future music teachers just over
4,000 hours.
So it may be that 10,000 hours, not 10 years, is the magic number.
Samuel Johnson (1709-1784) thought it
took longer: "Excellence in any department can be
attained only by the labor of a lifetime; it is not to be purchased at
a lesser price." And Chaucer (1340-1400) complained "the lyf so short, the craft
so long to lerne." Hippocrates (c. 400BC) is known for the excerpt "ars longa,
vita brevis", which is part of the longer quotation "Ars longa, vita
brevis, occasio praeceps, experimentum periculosum, iudicium
difficile", which in English renders as "Life is short, [the] craft
long, opportunity fleeting, experiment treacherous, judgment
difficult." Although in Latin, ars can mean either art or
craft, in the original Greek the word "techne" can only mean "skill", not "art".
Here's my recipe for programming success:
- Get interested in programming, and do some because it is fun. Make sure
that it keeps being enough fun so that you will be willing to put in ten years.
- Talk to other programmers; read other programs. This is more important
than any book or training course.
- Program. The best kind of learning is . To put it more technically, "the maximal level of
performance for individuals in a given domain is not attained
automatically as a function of extended experience, but the level of
performance can be increased even by highly experienced individuals as
a result of deliberate efforts to improve."
and "the most effective learning requires a well-defined task with an
appropriate difficulty level for the particular individual,
informative feedback, and opportunities for repetition and corrections
of errors." (p. 20-21) The book
is an interesting
reference for this viewpoint.
- If you want, put in four years at a college (or more at a
graduate school). This will give you access to some jobs that require
credentials, and it will give you a deeper understanding of the field,
but if you don't enjoy school, you can (with some dedication) get
similar experience on the job. In any case, book learning alone won't
be enough. "Computer science education cannot make anybody an expert
programmer any more than studying brushes and pigment can make
somebody an expert painter" says Eric Raymond, author of The New
Hacker's Dictionary. One of the best programmers I ever hired had
only a High School degree; he's produced a lot of , has his own , and made enough in stock options to buy his own .
- Work on projects with other programmers. Be the best programmer
on some projects; be the worst on some others. When you're the best,
you get to test your abilities to lead a project, and to inspire
others with your vision. When you're the worst, you learn what the
masters do, and you learn what they don't like to do (because they
make you do it for them).
- Work on projects after other programmers. Be involved in
understanding a program written by someone else. See what it takes to
understand and fix it when the original programmers are not
around. Think about how to design your programs to make it easier for
those who will maintain it after you.
- Learn at least a half dozen programming languages. Include one
language that supports class abstractions (like Java or C++), one that
supports functional abstraction (like Lisp or ML), one
that supports syntactic abstraction (like Lisp), one
that supports declarative specifications (like Prolog or C++
templates), one that supports coroutines (like Icon or Scheme), and
one that supports parallelism (like Sisal).
- Remember that there is a "computer" in "computer science". Know
how long it takes your computer to execute an instruction, fetch a
word from memory (with and without a cache miss), read consecutive words from disk, and seek to a new location on disk. ()
- Get involved in a language
standardization effort. It could be the ANSI C++ committee, or it
could be deciding if your local coding style will have 2 or 4 space
indentation levels. Either way, you learn about what other people
like in a language, how deeply they feel so, and perhaps even a little
about why they feel so.
- Have the good sense to get off the language standardization effort as
quickly as possible.
With all that in mind, its questionable how far you can get just by
book learning. Before my first child was born, I read all the
How
To books, and still felt like a clueless novice. 30 Months later,
when my second child was due, did I go back to the books for a
refresher? No. Instead, I relied on my personal experience, which
turned out to be far more useful and reassuring
to me than the thousands of pages written
by experts.
Fred Brooks, in his essay
identified a three-part plan for finding great
software designers:
- Systematically identify top designers as early as possible.
- Assign a career mentor to be responsible for the development of the prospect and carefully keep a career file.
- Provide opportunities for growing designers to interact and stimulate each other.
This assumes that some people already have the qualities necessary for
being a great designer; the job is to properly coax them along. put it more succinctly: "Everyone can be taught to sculpt:
Michelangelo would have had to be taught how not to. So it is with the
great programmers".
So go ahead and buy that Java book; you'll probably get some use out of it.
But you won't change your life, or your real overall expertise as a
programmer in 24 hours, days, or even months.
References
Bloom, Benjamin (ed.) , Ballantine, 1985.
Brooks, Fred, , IEEE Computer, vol. 20, no. 4, 1987, p. 10-19.
Hayes, John R., Lawrence Erlbaum, 1989.
Cognitive Psychology, 1973, 4, 55-81.
Lave, Jean, , Cambridge University Press, 1988.
Approximate timing for various operations on a typical PC:
| execute typical instruction | 1/1,000,000,000 sec = 1 nanosec
|
| fetch from L1 cache memory | 0.5 nanosec
|
| branch misprediction | 5 nanosec
|
| fetch from L2 cache memory | 7 nanosec
|
| Mutex lock/unlock | 25 nanosec
|
| fetch from main memory | 100 nanosec
|
| send 2K bytes over 1Gbps network | 20,000 nanosec
|
| read 1MB sequentially from memory | 250,000 nanosec
|
| fetch from new disk location (seek) | 8,000,000 nanosec
|
| read 1MB sequentially from disk | 20,000,000 nanosec
|
| send packet US to Europe and back | 150 milliseconds = 150,000,000 nanosec
|
Appendix: Language Choice
Several people have asked what programming language they should learn first.
There is no one answer, but consider these points:
- Use your friends. When asked "what operating system should
I use, Windows, Unix, or Mac?", my answer is usually: "use whatever
your friends use." The advantage you get from learning from your
friends will offset any intrinsic difference between OS, or
between programming languages. Also consider your future friends:
the community of programmers that you will be a part of if you
continue. Does your chosen language have a large growing community
or a small dying one? Are there books, web sites, and online forums
to get answers from? Do you like the people in those forums?
- Keep it simple. Programming languages such as C++
and Java are designed for professional development by large teams of
experienced programmers who are concerned about the run-time efficiency of
their code.
As a result, these languages have complicated parts designed for these circumstances.
You're concerned with learning to program. You don't need that complication.
You want a language that was designed to be easy to learn and remember by a
single new programmer.
- Play. Which way would you rather learn to play the piano: the
normal, interactive way, in which you hear each note as soon as you hit a key,
or "batch" mode, in which you only hear the notes after you finish a whole song?
Clearly, interactive mode makes learning easier for the piano, and also for
programming. Insist on a language with an interactive mode and use it.
Given these criteria, my recommendations for a first programming
language would be
or
. But your
circumstances may vary, and there are other good choices. If your
age is a single-digit, you might prefer
or (older learners might also enjoy these). The important
thing is that you choose and get started.
Appendix: Books and Other Resources
Several people have asked what books and web pages they should learn
from. I repeat that "book learning alone won't be enough" but I can
recommend the following:
- Scheme: is
probably the best introduction to computer science, and it does
teach programming as a way of understanding the computer science.
You can see on this book, as well as the . The book is
challenging and will weed out some people who perhaps could be
successful with another approach.
- Scheme:
is one of the best books
on how to actually design programs in an elegant and functional way.
- Python:
is a good introduction using Python.
- Python: Several
online
are available at .
- Oz:
is seen by some as the modern-day successor to Abelson & Sussman.
It is a tour through the big ideas of programming, covering a wider
range than Abelson & Sussman while being perhaps easier to read and
follow. It uses a language, Oz, that is not widely known but serves as
a basis for learning other languages.
<
Notes
T. Capey points out that the page on Amazon now has the "Teach Yourself
Bengali in 21 days" and "Teach Yourself Grammar and Style" books under the
"Customers who shopped for this item also shopped for these items"
section. I guess that a large portion of the people who look at that
book are coming from this page.
Thanks to Ross Cohen for help with Hippocrates.
