1. I don't think you have to understand everything. However, you should understand the parts that you use. 2. I find it critical to be able to rationalize abou

1. I don't think you have to understand everything. However, you should understand the parts that you use. 2. I find it critical to be able to rationalize about what the language, compiler/runtime and framework should be doing. This is never learned up front, but do take time periodically to understand what should be happening. For example, take 2 weeks to re-read JS the Good Parts. As you read, apply what you're learning to your code. 3. "the ways it's done". IME, "the way it's done" is too often "the way one engineer blogged about it and then 1,000 engineers reblogged without actually understanding why". Just because a solution is repeated over and over, does not mean its the right one for your situation. 4. the balance between understanding and productivity. Long term, the more you understand, the more productive you'll be. However, there is a time investment in the short run. Just balance the two based on your immediate needs. As for understanding, set a schedule of 30 minutes per night where you read. You won't learn everything at once, but it will happen over time. 5. Study JavaScript the language. JS, due to its async nature, is very different. Getting to know the language will make the Angular and/or any future frameworks you use a lot easier to think about.