> If you jump at a large project but lack the fundamentals you are going to wasting energy on stuff you shouldn't be. On the other hand, for many people (like

> If you jump at a large project but lack the fundamentals you are going to wasting energy on stuff you shouldn't be. On the other hand, for many people (like me!) it can be hard to feel motivated to learn a new programming language/framework/etc just for the sake of it (especially when you've got plenty of stuff going on already). (Note that I use "motivation" here in the immediate, executive function sense, not in the broader desire to do a thing sense.) In such cases, I have found that the best way to learn how to do what a large project requires is to first define the project that you want to accomplish that uses them, and then break that down into all the parts you need to learn to make it happen. The outcome is still "mastering the basics" before you actually take on the large project as a whole, but it can still look very much like trying to tackle the large project from some angles.