It can be a lot to take in. At least, it has been—still is!—for me. Good learning resources are critical. While I haven’t mastered either the language or how to learn it, I’m happy to share some things that have worked for me. Maybe they’ll help you as well!
Sample widely. There are so many resources for beginners out there, so many of them free or cheap, it’s hard to say what’s going to work the best, what’s going to most easily click for you. Books, videos, interactive classes; find what engages you, and dive on in. Ditch them when they get over your head. Try coming back later when you have more experience under your belt.
As you progress, don’t be afraid to continuously re-engage with fundamentals. As I gain more knowledge and understanding of the bigger picture, the more specific details come into focus, finding their place in my toolkit. It’s easy to miss things, only to later realize just how much you were leaving on the table—or didn’t even realize was there to be picked up.
Finally, get your hands dirty. Do things just to get them done, even if it feels like you’re doing them wrong; come back later when you’ve learned more, and try doing them better. I think it’s perfectly acceptable code the same way you might write a blog post: drafts improve with each pass. (I speak from experience here: I can easily fall into the trap of cycling through books and classes and blog posts and then forget to actually make things with what I learn, to help the knowledge stick. I’m working on it.)
I haven’t engaged with the CodeNewbie community as much as I might like, but I suspect that if you’re looking for more beginner-friendly resources, you’ll find people there excited to help you parse through the noise. (I do enjoy the podcast from time to time, and the weekly Twitter chats feel welcoming.)
As with all things dev-y, Google remains your friend. At least, until it’s not. Sorting through the noise can be a challenge. I’ve lost more than an hour of my life to terrible Google shame-spirals. It happens. (This feels like a loaded topic to me and I’m thinking about putting together another post or two about it. If you have any advice or tips or tricks for researching problem solutions in the age of Google, please chime in below, because I am all ears.)
Finally, of course: practice. Practice practice practice. I mean, don’t give up your life to it; take walks, pet animals, go to a restaurant now and then, and leave your phone in your bag. But still, making stuff, however good, however wrong, is one sure way to improve. Trust the process, but also enjoy the process.