DEV Community

Cover image for πŸ”₯ Roadmap Web Developer Front End 2020
Edwin Torres
Edwin Torres

Posted on • Updated on

πŸ”₯ Roadmap Web Developer Front End 2020

These notes are part of the recommendations of Andrei Neagoie in the Real Web Developer Roadmap 2020. I invite you to review The complete web developer in 2020 course or if you have some experience The complete junior to senior web developer in 2020 course and get your own insights. So, this an awesome feedback about what should we focus on in this 2020 as Web Developers. This first part covers the FrontEnd point of view in the roadmap, the BackEnd part is coming πŸ˜….

Important note: The links and notes marked with the πŸš€ are highly recommend

General recommendations

  • Master your IDE
  • Improve your basic fundamentals
    • Git / Github
    • Terminal skills
    • Learn to upload your files to your hosting and create your own domain
    • Learn more about JSON / gRPC

Front End

Web APIS provided by the browser πŸš€

HTML5 πŸš€

Responsive Mobile First πŸš€

CSS3 πŸš€


State Managment

SSR πŸš€

Helpers πŸš€

Build Tools

Web Components

Package Management

Popular libraries

JAM Stack πŸš€

Unit Test

End to End Test

Continuous Integration / Continuous Delivery

Back End

Static Hosting

Managed Hosting


Web Servers



πŸ¦• Deno

Python πŸš€

API Consumption



Relational Databases πŸš€

NoSQL Databases πŸš€

Managed Databases



Machine Learning

Web Assembly πŸš€

PS: If you are starting your Web Development career, I suggest you can start with this Complete Web Developer 2020 Course by ZTM and get a 10% discount using that link.

PS2: To review more post like this, I invite you to my blog πŸ€–.

Cheers and keep learning! 🍻

Top comments (11)

rawbrt profile image
Roberto DΓ­az

Oh my. Here we go again.


People doing this kind of roadmaps should specify the degree of mastery you have to have to accomplish it. Also their limitless-style drug dealer phone number to start learning.

codesandtags profile image
Edwin Torres

Well, after reviewed the experience and trajectory of Andrei Neagoie, I can say he has that kind of mastery of the things they talk about. And regarding list and roadmap, only are opinions based on what is demanding the industry, some statistics based on surveys.

Regarding list and roadmap, only are opinions based on what is demanding the industry, some statistics based on surveys and finally, I think you don't need to learn 100% everything, time is limited to learn everything in the world, you only need to know that exists some technologies and they are demanded by the industry is enough to choose what you should be focused. But in the end, it is not a one size fits all.

rawbrt profile image
Roberto DΓ­az

Yeah, I don’t judge the author! I mean that there’s this trend that implies that, to be a web developer (or frontend, backend, etc.) you need to know a tree of technologies with infinite branches.

The reality for lots of us is that we are going to stick to a tech stack, easily, for 2-3 years.

And I won’t talk about consulting or big companies, where you usually work developing and mantaining legacy solutions.

My two cents: It’s ok to now what comes out, updates, whatever. But it’s a lot more valuable to develop truly deep expertise in a specific stack that jump over any new framework or library.

You are going to be a lot more valuable if you are an ace in i.e. MEAN or MERN stack, than knowing how to do a slightly complex hello world in 8 trendy new tools.

Thread Thread
codesandtags profile image
Edwin Torres

Sure!! To be honest, after almost 7 years as Developer in (Back, Front and Mobile) the most important thing I've learned is:

We need to focus in the fundaments and get knowledge for the long term.

It does not make sense, learn every framework, library, trend, and fall in the "fatigue". Because one more time, time is limited, and we should use it wisely.

Nice comment @roberto ! πŸ’ͺ🏼

Thread Thread
rawbrt profile image
Roberto DΓ­az

Totally agree!

Thank you, Edwin!

maciejcieslik profile image
Maciej Cieslik

From my experience, Hugo is faaast but has cons, for me it's good only for static+cloud cms and simple stuff, need more plugins. Deployment on heroku is a breeze (1-2min max). Elm is a dead end to me and I think deno will not be good for production this year. Cheers and thanks for good list.

codesandtags profile image
Edwin Torres

In my personal experience and opinion, I've used Gatsby and Jekyll, however recently I've moved 100% to Gatsby, by its simplicity and amount of plugins.

Maybe DENO is still in his first step, however as said, we don't need to use DENO because he says, is a good point to have it in this roadmap. :) . We'll wait for the next year.

Thanks for your comment and your opinions @Maciej! :D

maciejcieslik profile image
Maciej Cieslik

I'm curious about deno and yet my feelings are totally ambivalent, I'll wait some time and see where it going. Cheers :)

saint4eva profile image

Nice. However, can you including the following to make the list logical?

Serverless => Azure Functions
Mobile => Xamarin Forms.

aminda profile image

thanks ...

codesandtags profile image
Edwin Torres

You're welcome! :)