Originally Posted by
freedompeace
Put it this way - I have never read a programming book in my life, and I won't ever do it. That's just the most stupid way to learn a hands on subject. (Of course, this is subjective)
Anyone want to learn a tradie skill by reading a book about it?
To a Point (on Code-Monkey Level) this is true; i.e. you will NEVER learn any decent level of programming if all you do is read, and never put what you read into practice. You HAVE to actually do the work for it to 'stick'..
However, when you expand into more complex software architecture (e.g. more than the 1 Class / 3 function crap you see all over this site) you better read (whether that be on paper on digital is up to you) & study things like Design Patterns - Half the time (or more) the design aspect is not even dealing with a computer but about abstract relational concepts that only down the line get turned into code by previously mentioned code-monkey based on spec/design by the architect.
Besides, a lot of people like to read up on things when they're NOT behind a computer (e.g. commuting or whatever) so that next time they have a clearer picture in their head of what to do/try/learn next.
Kind of like myself...
?
Makes me look bad 
. It's a lot easier if you have a project on the go though, seeing as you know what you need haha.
Mr. Perfect. I don't care as long as I will learn something new.