Very excited that you posted this article, I am just beginning to start building things to add to my portfolio/github. It was somewhat mentioned in the project ideas, but when do you think the appropriate time or situation is to begin adding frameworks, libraries, etc., versus sticking with the basic tools (For web, HTML, CSS, plain JS)? Is it just until you believe you have a good grasp of those and have some work to back up the confidence in those skills?
I like the idea of getting comfortable with HTML, CSS, and plain JS first, so I'd agree with your statement about having a good grasp of those along with some projects to back up your skills. It's so much easier to learn a framework when you know those languages.
Once you're comfortable with the fundamentals, the next step is to look at companies you're interested in and see what tech most of them seem to be using. If there's a framework that keeps popping up, experiment with that and build a small project with it. That way you'll have an idea of how to use it, and you have evidence you can point to that you've used it.
If you ever find yourself unsure what to spend time on, you won't go wrong sharpening your HTML, CSS, and JS since these automatically make you better at many frameworks at once.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Very excited that you posted this article, I am just beginning to start building things to add to my portfolio/github. It was somewhat mentioned in the project ideas, but when do you think the appropriate time or situation is to begin adding frameworks, libraries, etc., versus sticking with the basic tools (For web, HTML, CSS, plain JS)? Is it just until you believe you have a good grasp of those and have some work to back up the confidence in those skills?
I like the idea of getting comfortable with HTML, CSS, and plain JS first, so I'd agree with your statement about having a good grasp of those along with some projects to back up your skills. It's so much easier to learn a framework when you know those languages.
Once you're comfortable with the fundamentals, the next step is to look at companies you're interested in and see what tech most of them seem to be using. If there's a framework that keeps popping up, experiment with that and build a small project with it. That way you'll have an idea of how to use it, and you have evidence you can point to that you've used it.
If you ever find yourself unsure what to spend time on, you won't go wrong sharpening your HTML, CSS, and JS since these automatically make you better at many frameworks at once.