Teach Yourself Programming in Ten Years
Source: Teach Yourself Programming in Ten Years
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 #-Link-Snipped-# at #-Link-Snipped-#: #-Link-Snipped-# #-Link-Snipped-#and got back 248 hits. The first 78 were computer books (number 79 was #-Link-Snipped-#). I replaced "days" with #-Link-Snipped-# and got remarkably similar results: 253 more books, with 77 computer books followed by #-Link-Snipped-# 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 #-Link-Snipped-#, 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 #-Link-Snipped-# could mean:
Researchers (#-Link-Snipped-#, Teach Yourself Programming in Ten Years, #-Link-Snipped-#, Teach Yourself Programming in Ten Years) 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. #-Link-Snipped-# 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:
Here's my recipe for programming success:
Fred Brooks, in his essay No Silver Bullet identified a three-part plan for finding great software designers:
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.) #-Link-Snipped-#, Ballantine, 1985.
Brooks, Fred, #-Link-Snipped-#, IEEE Computer, vol. 20, no. 4, 1987, p. 10-19.
Bryan, W.L. & Harter, N. "Studies on the telegraphic language: The acquisition of a hierarchy of habits. Psychology Review, 1899, 8, 345-375
Hayes, John R., #-Link-Snipped-# Lawrence Erlbaum, 1989.
Chase, William G. & Simon, Herbert A. #-Link-Snipped-#
Lave, Jean, #-Link-Snipped-#, Cambridge University Press, 1988. Answers
Approximate timing for various operations on a typical 1GHz PC in 2001:
execute single instruction 1 nanosec = (1/1,000,000,000) sec fetch word from L1 cache memory 2 nanosec fetch word from main memory 10 nanosec fetch word from consecutive disk location 200 nanosec fetch word from new disk location (seek) 8,000,000 nanosec = 8 millisec Appendix: Language Choice
Several people have asked what programming language they should learn first. There is no one answer, but consider these points:
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:
T. Capey points out that the #-Link-Snipped-# 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.
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 #-Link-Snipped-# at #-Link-Snipped-#: #-Link-Snipped-# #-Link-Snipped-#and got back 248 hits. The first 78 were computer books (number 79 was #-Link-Snipped-#). I replaced "days" with #-Link-Snipped-# and got remarkably similar results: 253 more books, with 77 computer books followed by #-Link-Snipped-# 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 #-Link-Snipped-#, 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 #-Link-Snipped-# 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? #-Link-Snipped-# 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.
Researchers (#-Link-Snipped-#, Teach Yourself Programming in Ten Years, #-Link-Snipped-#, Teach Yourself Programming in Ten Years) 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. #-Link-Snipped-# 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 Learning by Doing. 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." #-Link-Snipped-# 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 #-Link-Snipped-# 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 XEmacs: The next generation of Emacs Internet for people, not profit — Mozilla, has his own #-Link-Snipped-#, and made enough in stock options to buy his own Dna Lounge.
- 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. (Teach Yourself Programming in Ten Years)
- 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.
Fred Brooks, in his essay No Silver Bullet 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.
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.) #-Link-Snipped-#, Ballantine, 1985.
Brooks, Fred, #-Link-Snipped-#, IEEE Computer, vol. 20, no. 4, 1987, p. 10-19.
Bryan, W.L. & Harter, N. "Studies on the telegraphic language: The acquisition of a hierarchy of habits. Psychology Review, 1899, 8, 345-375
Hayes, John R., #-Link-Snipped-# Lawrence Erlbaum, 1989.
Chase, William G. & Simon, Herbert A. #-Link-Snipped-#
Lave, Jean, #-Link-Snipped-#, Cambridge University Press, 1988. Answers
Approximate timing for various operations on a typical 1GHz PC in 2001:
execute single instruction 1 nanosec = (1/1,000,000,000) sec fetch word from L1 cache memory 2 nanosec fetch word from main memory 10 nanosec fetch word from consecutive disk location 200 nanosec fetch word from new disk location (seek) 8,000,000 nanosec = 8 millisec 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.
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: #-Link-Snipped-# is probably the best introduction to computer science, and it does teach programming as a way of understanding the computer science. You can see #-Link-Snipped-# on this book, as well as the #-Link-Snipped-#. The book is challenging and will weed out some people who perhaps could be successful with another approach.
- Scheme: #-Link-Snipped-# is one of the best books on how to actually design programs in an elegant and functional way.
- Python: #-Link-Snipped-# is a good introduction using Python.
- Python: Several online BeginnersGuide - Python Wiki are available at #-Link-Snipped-#.
- Oz: #-Link-Snipped-# 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. <
T. Capey points out that the #-Link-Snipped-# 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.
Replies
-
silverscorpionThat was just amazing.
Though a bit long, it was a great read.
Offered several insights into the ways of good programming. Thanks!! -
Madiha MahmoodNo i dont know. its a new information. tell me about this.
-
durga chBoy!
This is just awesome. Its a constant reminder " practice makes you perfect.. keep doing it until you master it"
By the way , this looks like the ORIGINAL article
Teach Yourself Programming in Ten Years
😡 was reference to the author forgotten? -
raj87verma88A link should have been provided. If what Durga says is true then this is just copying, worse than plagiarism.
-
Madiha Mahmoodmy friend send me this article. and i think to share this wid u ppl.
-
Madiha Mahmoodand yes its also a orignal article.
-
durga chhmm, Madiha , since its your friend who forwarded it to you, may be you were not aware.
But we do follow few ethics here 😀
takecare from now one -
shalini_goel14Hey Madiha ! Thanks for sharing good tips on getting good hands on programming
[PS: * No criticisms OK *
I guess "CE Google search experts" should alert people through PMs 😛 so that rest of CEans don't get affected and still keep on getting good information to read (as provided by slashfear). I can guess why we cannot see any more informative posts from his side anymore. ] -
silverscorpionWell, there's nothing wrong in putting up a link to the original when the poster has "forgotten" to give that link.
And we are not thrashing him for not doing it. Just a friendly remainder, that's all..
Meanwhile, I think that the article does contain a link to the original. Just that it's in the middle of the article, it's not listed as the source.
😛😛Madiha Mahmood- 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. Teach Yourself Programming in Ten Years
-
Ashraf HZlol @ SS
Sorry for the heat, Madiha. As SS said, not meant to be a thrashing 😀
It is clear that this was from a some other source, and as Durga mentioned, a mention of the link would have sufficed.. and if a source could not be identified, mention where you got it from. The issue is cleared up now of course. Thanks for the article!
Slashfear's case is an issue of a different nature and we will not discuss it here 😀
Back this thread. I used to read those Teach Yourself programming books for quick revision, after a long period of stagnation. They are pretty useful!
And there are some unfair judgments in this article. For example.. the books that say teach yourself in 24 hours do not necessarily mean you can learn the concepts in a day. It means, there are 24 hours worth of material to cover. So lets say you dedicate 1 hour per day, 5 days a week. So roughly, you'll take about 5 weeks to finish the lessons. Similar concept with "3 days" etc.
Can't really judge people who buy those books as those desperate to learn concepts quickly. Its up to them how fast they want to learn it. The authors of those books are merely providing flexibility.. for those who capable to grasp concepts instantly, or those who prefer to take their time, or those who are using them for revision 😉 -
Madiha Mahmoodok guyzzz next time i takecare. ok.
-
jhbalajiAfter Studying all this things mate...
You will not be you...
I mean a Geeky Geek so be careful... -
safwanThanks madiha for sharing this article.
ie. becouse of this when ever i post something in my blog or some posts i mention it. -
Manish Goyalnice article Madiha
good work -
MaRoGood start Madiha..I assumed you are an Egyptian from your name & I understood you are working at IBM from your job title..Engineer at IBM in Egypt?
Guys, don't wait referring to the source from Egyptian users 😛
You are reading an archived discussion.
Related Posts
HI
DEAR FRDS
IAM RAHUL .IAM PERSUING MY ELECTRICAL AND ELECTRONIC ENGG FROM UTTAR PRADESH TECHNOLOGICAL UNIVERSITY .
I NEED SOME ABOUT THE PROJECTS THAT CAN BE DONE IN THE...
Im just discussing a new idea of a project ::
A mobile program that allows you to locate friends using the gps system and you can video call them using...
Dear All,
I am new to this forum. I have been trying to develop an NIDS. but i have stucked in verifying protocol stack. can any one send me details...
I firstly thyanks about what you did!i some information on bluetooth,really very intresting.am in year four electronics and telecomminication at KIGALI SCEINCE AND TECHNOLOGY IN RWANDA.I would like to ask...
can some one help me in choosing my career in robotics i am doing my under graduation with ece branch.
thank you