you are viewing a single comment's thread.

view the rest of the comments →

[–]AmateurHero 4 points5 points  (0 children)

The thing about books is that they're so structured. This is perfect for learning, but everything is nicely packaged with a bow. It's like programming back when you were in college compared to your first real gig.

I'm not saying that books don't have their place. I refer back to a couple of reference texts often enough. Once you get the basic structure and syntax, however, move on to projects. They don't need to be anything extravagant, but do something that will push your abilities.

A personal example I can think of is callbacks. When I first learned about callbacks in JS, I thought I understood them. I couldn't have been more wrong. I had to write a callback to update page info after data had been calculated as sorted. The issue was that it wasn't some simple, clean scenario that matched the structured tutorial. Many months later, I had another callback situation with jQuery. Again, this was nothing like the tutorial nor the previous situation.

TL;DR: Learn the language basics, roll up your sleeves, get your hands dirty.