Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

Do you find that it is better to learn through reading books or to just jump straight into a project and pick up what you need to know using the web, or some combination of both?

share|improve this question

closed as primarily opinion-based by gnat, MichaelT, GlenH7, Kilian Foth, World Engineer Oct 22 '13 at 0:48

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

    
For me the best way is to start doing. But, everyone learns differently. –  Jeff Jun 16 '11 at 20:08
    
A little from column A and a little from column B :) –  Gary Buyn Jun 16 '11 at 20:57
add comment

7 Answers

up vote 13 down vote accepted

False dichotomy; I routinely work on a project while reading a book.

I will say this: if you just read a book without actually programming anything then you are not gonna learn the language. Now whether you're reading from a book or from the web while working on your project matters little; obviously you want a good resource and not a crappy one, but there are both good and bad learning resources in both book form and on the web.

share|improve this answer
    
Sorry, edited to adress that issue. –  Akromyk Jun 16 '11 at 19:51
    
I tend to find that I treat books in a linear way. I rarely use them as resource and instead attempt to read them from front to back. Am I taking the wrong attitude with them? –  Akromyk Jun 16 '11 at 19:56
    
I don't know about "wrong" attitude, just different from me. I always treat every programming book as a reference text, because I already know the basics they'll be covering in the first few chapters. –  jhocking Jun 16 '11 at 19:57
    
@user: No way. The first chapter is almost always insanely boring. Then there will be (chapter on language feature you have no use for (usually graphics, for me)). –  Satanicpuppy Jun 16 '11 at 19:59
1  
Incidentally, the best books will actually encourage you to program something while you work through the book. They'll sprinkle assignments throughout the text. –  jhocking Jun 16 '11 at 20:01
show 1 more comment

Well, assuming you already know how to program, and are just jumping into a new language, I'd recommend just starting and using the web. You're really just playing around with features and syntax, and it's easier to do that if you're actually doing something. Not to mention that you'll retain the knowledge longer if you actually use it for something.

If you're new to the whole idea of programming, it'd be better to read a bit first. There are a lot of bad habits that you'll be glad you avoided. I got started by reading other peoples code, and it's left me with some weird quirks to the present day (25 years later), despite my later formal education.

share|improve this answer
    
Thanks. In my case I already have a decent foundation in programming theory. –  Akromyk Jun 16 '11 at 19:52
add comment

The most efficient way to realize an investment in theoretical knowledge is to put it into practice. If you only read books, it will take you far, far longer to actually understand the concepts. You may never achieve a practical understanding. On the other hand, if you only write projects and increase the bounds of your knowledge, you will merely ingrain the level of understanding you currently have.

Find a balance between the two that works for you. Experiment with your experiments so that you can learn how to learn and improve your skill at improving your skills.

TL;DR: You have to do both. Read books to expand your theoretical understanding. Ship things to turn theoretical understanding into practical understanding.

share|improve this answer
add comment

I think it would depend on the type of learner you are. If you are 'see than do' type of learner, then perhaps reading a chapter in the book then trying to apply what you learned might be best.

If you are a 'learn by trying' type of person, then maybe try doing something and look up stuff as you need it.

How strong are you at programming? Are you learning to code from scratch or do you have a language to draw from. Learning to program is more difficult than learning a new language. Once you have a language as a reference and you have a knowledge base for programming to draw on, learning a new language becomes easier.

share|improve this answer
    
I've taken a couple of classes in Java and have the concepts down, but I have little practice in actually programming much code. In my life I've been much more of a 'learn by trying person', but my lack of confidence in programming causes me to behave as a 'see then do' learner. –  Akromyk Jun 16 '11 at 20:20
    
@user27998 - then try something. Write a simple game from scratch by yourself. You build confidence by doing, not by waiting. :) –  Tyanna Jun 16 '11 at 20:26
add comment

If forced to pick one, I would jump into a project. Many books on a language are similar, but you may have picked one that had a special section and would read that first. Maybe you're more interested in the video capabilities of an iPhone or database interaction in .NET.

This is one of those times when a quality mentor is useful.

share|improve this answer
add comment

I like to work through a book while writing code for each concept in the book. Depending on whether the book has good examples, I'll either use the examples in the book or program my own. I find that I retain the knowledge better if I'm coding and taking notes along with the book.

After reading through the book, I'll tackle a lager project. I find it easier to switch to online documentation at this point.

To have maximum knowledge retention, you need to process the knowledge multiple times in several different ways.

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.