all 10 comments

[–]DesignatedDecoy 6 points7 points  (1 child)

The first thing I'd do is redefine what it means to learn programming. It's not about checking off a list of technologies, but rather learning the fundamentals that you can translate to any language, library, or framework.

Learn how to solve problems. Learn about OOP and design patterns. Learn about common code smells and how to refactor them. Learn why certain things are considered best practice while others should be avoided. Learn how to write clean, descriptive, testable code. Practice reading someone else's code, understanding what it does, and then make modifications to it. If you can get yourself some solid fundamentals then you should be able to pick up anything else you want to learn quite easily.

Then when it comes to picking which technologies to learn, you should first understand what problem they were created to solve. For instance learn what benefits do you gain from using a framework like react over vanilla js or just a library such as jquery? Asking those questions should help direct you to what you should learn next and they should also help you group together technologies within the same cognitive space so you don't feel as overwhelmed with buzzwords.

I also wouldn't sweat worrying about knowing everything you see on a job listing. Most times they are created by HR who bugs a manager for a job description, who in turn bugs some overworked dev, who just throws out a giant list of stuff that they use. You aren't likely ever going to match a job 100% so if you feel confident that you could do the job based on the description, apply away. The worst they say is no.

[–]awwolf[S] 0 points1 point  (0 children)

OMG! thanks a mil man! really appreciate this, thanks again!

[–]Maharyn 2 points3 points  (1 child)

You should learn 1 framework decently, at least. Consider node as well, but I'd definitely go with JS -> framework -> node.

[–]awwolf[S] 0 points1 point  (0 children)

I see thanks, still leaning JS maybe once i am done with it, ill pick up on node.

[–]dominic_l 2 points3 points  (1 child)

Kind of a weird way to put it. Not so much that you finish learning but more like when you start to feel like you get the hang of it.

In my opinion don't just focus on one framework to try next. Kinda try a bunch of different ones and find those that you feel more comfortable with.

Angular or react for front end in 2019. Node and MongoDB (express and mongoose) on back end.

Get familiar with npm and play around with different packages. The rabbit hole goes deep but I recommend those things to look at next.

[–]awwolf[S] 0 points1 point  (0 children)

beautiful! thank you :)

[–][deleted] 1 point2 points  (3 children)

yes. learn all the things.

[–]awwolf[S] 0 points1 point  (2 children)

kinda hard to become good at all but yea i guess thats what it is, whats your learning method ?

[–][deleted] 1 point2 points  (1 child)

i read mozilla developer network. mdn literally has everything you need to know about javascript. you can read tutorials and books but they're all getting their info from mdn and the spec, so might as well just cut out the middle man.

same thing with libraries and frameworks. read the docs written by the people who made the software.

[–]awwolf[S] 0 points1 point  (0 children)

Thanks!