News for hackers. Stuff that matters.
Re:How I Read Programming Books by kylemaxwell on Tuesday January 08, 2013 @09:56AM (#5026449)
The "typing code out" is important. A lot of us learned just this way in the early 80s, because that was the only way we could get the source: buy a magazine or a book that taught, say, game programming in BASIC, and then type in code. The inevitable syntax errors made you spend time going back through to figure out what you did wrong, not to mention the time you spent actually looking at each line.

Downloading the code from a book's web site has nowhere near the same effect, even if it "feels" more efficient.

Re:How I Read Programming Books by natep on Tuesday January 08, 2013 @10:25AM (#5026585)
I try to do the same thing in lectures. Unless I'm late or the lecturer is a particularly fast talker, I can usually process the information to the point where I'm writing my current understanding in my own words. Much better for me than taking dictation for an hour.
Re:How I Read Programming Books by bornhuetter on Tuesday January 08, 2013 @10:43AM (#5026690)
> I can usually process the information to the point where I'm writing my current understanding in my own words.

Can you explain what you mean by this?

Re:How I Read Programming Books by Swizec on Tuesday January 08, 2013 @11:00AM (#5026784)
He means he's taking notes.

Rather than painstaikingly writing down everything the lecturer says. Which would be stupid anyway, that's what audio recorders are for.

Re:How I Read Programming Books by LaRakel on Tuesday January 08, 2013 @11:43AM (#5026992)
You can't skim over audio recordings
Re:How I Read Programming Books by Posibyte on Tuesday January 08, 2013 @12:55PM (#5027347)
I ran through my audio recordings in 1.5x speed the week before finals when I was studying. It's kinda like skimming.
Re:How I Read Programming Books by uriloran on Tuesday January 08, 2013 @10:24AM (#5026578)
Jep, you are absolutely right. If you type everything for yourself you remember and understand everything a notch better too. If you just copy & paste you won't really look at the code...