Msg#: 4391515 posted 8:58 pm on Nov 27, 2011 (gmt 0)
Msg#: 4391515 posted 11:51 pm on Nov 27, 2011 (gmt 0)
Analogy that springs to mind: How many people around here first learned HTML in the '90's? We can do a whole lot more, but that 1998-vintage HTML still works, and it's a solid foundation for the stuff we've added later. That's assuming, of course, that you learned correct rules and good habits back then.
Computer development tends to go by hiccups-- think "punctuated equilibrium"-- and I can't think of any major hiccups in the past two years.
Msg#: 4391515 posted 2:26 am on Nov 28, 2011 (gmt 0)
I agree, 2009, 2010 publications should still be fairly relevant with respect to the basics.
I just feel that for someone who's not used to the technical jargon used in these languages, a dummies book written in layman terms would be more easily understandable and they tend to explain the nuances of why you'd want to do this over that, how to access objects, how and when to connect objects and methods and so on in a way that a lay person can quickly understand.
Books that are written by software engineers tend to be written in a more dry and technical fashion and they assume you can grasp and deduce the nuances on your own.
Unfortunately, not ever one learns in the same way and every one is academically or technically proficient.
Msg#: 4391515 posted 6:10 pm on Nov 28, 2011 (gmt 0)
I would say any way you learn is what's right for you (relevant to your PHP question too.) When I first started learning JS I went with a book. Did all the examples. Front to back. Learned a lot.
Then I came to places like this web site and found much of what that author wrote was wrong, or if not wrong, certainly not efficient. I was p***ed. This guy was a professor at a university and made millions on his stupid book. Most of it was wrong! Eventually my "takeaway" was the basic under structure of the language, so I guess it worked out OK.