I am following the popular front-end roadmap in roadmap sh.
I learned basic html css and convert psd to css with simple templates.
Now I can’t decide what to learn and when.
How should I proceed, is there a more detailed roadmap?
I am following the popular front-end roadmap in roadmap sh.
FCC already has a suggested roadmap. If you look in the upper left there is a button to “Visit the Curriculum”.
More general advice is to just keep learning. Keep learning and building things. Then learn more things and build something else. Then learn more complicated things and build more complicated things.
There is no “magic roadmap”. There are many good possible roadmaps. I expect most any roadmap you find online is going to be at least pretty good.
I just wanna know what i will learn next.
I can’t answer that because I don’t know that because I don’t know what your level in those are or what your objective is.
I suggested a roadmap - it’s in the upper left of your screen.
Would it be bad if you continued learning HTML/CSS? No. If you stay on it too long, maybe. Would it hurt you if you move onto JS? Assuming you have some basic skills in HTML/CSS, then no, not at all. You can always come back to work on those if you need to. You will probably keep learning about them anyway, as you build things. “Learning” these things does not mean “I learned everything and am done with this”. It often means, “I learned the basics and I know what is possible and I can look up the details if I need to”.
Don’t worry so much. Just learn. There is no perfect path.
The idea of following a roadmap follows along with the idea there is a “right” way to go about things. Or that following a roadmap means it will be easier to learn things “in order”.
The reality is that there isn’t really an “order” to things. Everyone’s existing background is different, their timelines are different, their concerns, their likes, and their dislikes are different. And most importantly technology is more a mashup than a clear guide, it never promised to be “roadmappable” with clear guidelines on what comes after what.
Ultimately you need to learn, at least a high level, basically everything. Furthermore you need to keep up, as there are always new things to learn today and tomorrow. This doesn’t mean you need to learn everything in depth, or try to become an expert or “wait” to learn more about something before “moving to the next thing”. Rather, the most important thing is to realize where you are on your own roadmap.
This means understanding if you move from technology A, to technology B, you roughly know how those 2 connect, used, and why. This is so you can “jump” between what your learning and understand the context around them. You might not be an expert on either, but you can always “jump back” to previous things you’ve learned to learn what you need.
Its that “path” that most seek out when it comes to getting some kind of detailed roadmap, but due to all the variables (pun not intended ;D) its not as clear cut most of the time. Sure you can follow it as a guide to get a sense of what your doing.
You could also just find a high level idea (learn the MERN stack), and start hacking away at that and see where it takes you. For example, if you learn React, you’d probably find 50 different other technologies tied to it you could possibly learn. If you spend time doing that is another story, which goes back to understanding how they relate to what your doing.
Long story short, there is a lot to learn. Its less important the order you try to learn it, and more that you go out and learn anything and everything.
Stay curious, stay open, and don’t mind the details to much. You need that context, so you can focus on whats important. Just whats important is usually different from person to person.
Good luck, keep learning keep building
I agree with what Jeremy said. I also was puzzled by this line:
On the surface, sure. But the difficulty comes with your definition of “learn”. It would take a long time to “learn” HTML. I’ve been a professional dev for more than three years now and I feel like I am still “learning” CSS.
I would replace “learn” with “get a basic level of comfort”.
Rather than try to convince the experienced coders that they are wrong, maybe, I would suggest, you could acknowledge that you are a beginner and put aside your assumptions about how coding should be learned and listen to the more experienced people. It’s just a suggestion.
Just learn. Don’t get caught up on one thing. Keep moving forward. If you strive for perfection, you will never get anywhere - just try to keep getting better.
I have no idea what ‘writing the template’ means.
If you are working on a project, go ahead and finish that project. Or if you think you need to learn additional skills to do the project in a better way, go ahead and do that.
You’re totally overthinking this.
I’m not sure at this point what you really want us to say to you, but you seem to have some specific certain opinion you want us to validate. Not knowing what this specific opinion is that you want validated, we’re just giving you solid advice about learning programming.
Thanks for your time. keep learning.
I agree 100% with all that Jeremey and Brad have said here, but for a slightly different angle…
Are you doing a curriculum or trying to learn by building a project. You keep talking about curriculum but this makes me think that you are just building something. I’m not a big fan of the “learn by building” approach when you are beginning - it is too easy to pick up bad habits and to miss things.
But if you’re going to do it…
If you want to focus on JS for a while, sure, go ahead. If you are “not done learning HTML/CSS”, then that’s still OK. You aren’t going to do any damage. (And I point out that you will still be learning HTML/CSS for years.) If you want to shore up your HTML/CSS knowledge first, that’s fine too. Again, the biggest danger is getting stagnate and not moving forward.
Just pick one. It’s like a person given a bowl with a scoop of vanilla and a scoop of chocolate ice cream. They sit there debating with themselves which it is best to eat first or if they should alternate. They mull it over for hours and by the time they decide, the ice cream melts. Just make a choice. Don’t worry if it is “the best” decision. Accepts a good decision. And realize that there may not be a “best” decision.
Seems to me if you need to use JS then you need to learn JS. I suppose you could try to find some code that does what you want it to do, or close enough, and then modify it for your needs, getting by with as little knowledge of JS as possible, just enough to get it working. Or perhaps you could use a library like jQuery to reduce the learning curve somewhat? But if you want to do web development professionally then you will need to know JS, there is no getting out of that.
The ice cream is melting. Just make a choice. As long as you keep learning, it is a good choice. Just about the only wrong choice is to keep worrying about the perfect path so you slow your progress. Just keep learning.
But I have nothing more to add to this, I’m out.