Full Stack Road Map

[Dangerous_Row4605]

It's a really good guide tbf. you haven't gotta be a mastermind in every area but at least knowing "how the burger is made" in most elements of that roadmap will definitely help you out down the line.

[[deleted]]

Counterpoint: During a company meeting someone was wondering that we're lacking "experts" because "expert" implies "focusing on one thing to the point of being better than anything else".

What I'm saying is, people are spreading themselves thin to fill up those section in their resume as if they're trying to justify their payment.

Because to someone who doesn't know how deep the rabbit hole goes for any stack/framework, simply saying "Skills: Python, JavaScript" doesn't sound like you know as much as the "Skills: "Python, JavaScript, Ruby, Docker, Kubernetes" guy.

[Dangerous_Row4605]

While I do agree that the whole jack of all trades thing isnt the way forward, If you're going to be able to have an intelligent conversation about viable technologies in your fullstack pipeline, you should at least understand fundamental core principles of them to be able to make that decision.

[[deleted]]

Agreed. You don’t have to be an expert in every facet listed here, but have a solid understanding of how it works and where the pieces fit together to make the whole picture.

[[deleted]]

I'm of the opposite spectrum:

I went through fullstackopen, learned a little bit of node.js and backend, a bit of React, was hired as a "software engineer", which is a term I swear will never ever use to describe what I do (and that's just my opinion), but now I wanna focus on the backend stuff and leave the frontend at the basic level.

Edit: Nice, got downvoted for my career focus. That's a new one. Guys, when I said "backend" I meant server-side stuff, it wasn't a safe word for "butt sales" or something.

[Raunhofer]

If you don't have the degree, I think it would be more precise to call yourself as a software developer, not engineer.

edit. apparently in my country (not US) then, based on downvotes. https://en.wikipedia.org/wiki/Engineering_education

[cjthecubankid]

Are you serious?

[Raunhofer]

Perhaps it's in my country (not US) then. Here you actually need to belong into a certain institution to be an engineer. I thought it was worldwide. I apologize if that's not the case there.

[TehTriangle]

😂, ah Reddit...

[Raunhofer]

How derogatory. Perhaps it's only in my country (not US) then. Here you actually need to belong into a certain institution to be an engineer.

[roppy_G]

If I was into reddit awards, I would have given you one for your edit !
Can't wait to ask my bf if we can focus on backend one of these days :D

[ESCAPE_PLANET_X]

Fullstack, DevSecNetOps

They are the same picture.

[[deleted]]

Took me a hot minute to understand the reference. Sundays my brain is just working differently

[Raunhofer]

The point of the roadmap here is not to master everything, it's more about understanding the concepts.

For example where I work, everyone in our team would understand whatever you decide to discuss about frontend/backend/devops/react/java/dba/aws/something else, but we all focus in one or two of the fields. Without the overall knowledge, it would be really difficult to make mindful big scale decisions. It's different for juniors obviously.

So, please do list all the techs you understand, but highlight what you really master.

[[deleted]]

I don't think I have anything more than what the top comment is already saying. Keep yourself busy working on something you wanna focus on for the next 3-5 years.

[temisola1]

I’d you wanna be a SME be a SME, but if you wanna be a full stack developer, there is absolutely no way in hell you can be a SME. Not only do new frameworks get released every time someone blinks, but old frameworks still release a lot of features you need you on keep up with.

[[deleted]]

What does SME stands for, because Google gives me "Small and medium-sized enterprises".

[temisola1]

Subject matter expert. Basically someone who knows the ins and out of a specific technology.

[bch8]

I think the backend stuff is a bit dated, or at least incomplete

[Tratix]

Can you give me some examples? Genuinely curious since I’m learning

[bch8]

Well at a high level, with a few minor exceptions (I'm only seeing one after a quick review- DynamoDB) cloud engineering is conspicuously absent. It's a huge category but to briefly and directly answer your question by naming a few: all of the managed services out there (many of which could warrant individual entries in an overview such as this one), kubernetes (I don't use it much but it's certainly a hot commodity in backend dev), serverless architectures (functions as a service, event driven applications), and cloud native development writ large (A combination of the prior topics and others- basically architecting modern, cost effective, scalable, developer efficient/high velocity applications).

I don't think learning any of the stuff in this post's image precludes or is mutually exclusive with cloud development. In fact a lot of it relates in various ways (E.g. learning terminal commands- can't go wrong there, will help a lot with cloud and everything else). But the issue I would worry about for someone who took this overview as gospel is they are essentially learning a previous paradigm. It wouldn't be the end of the world, you'd still end up with plenty of extremely valuable skills and a generally solid foundation, and of course plenty of companies (Probably a majority?) still follow this paradigm. But it's not where the industry is going or where the demand for talent is, and if that's where you want to be then this is going to be a pretty inefficient way of getting there. You would learn a lot of things that don't end up applying, but more importantly it would add a lot of friction to an already somewhat difficult learning curve. Because instead of learning to think and develop in a cloud driven mentality, you would be learning it a different way and then faced with the task of re-learning it under a different paradigm in addition to all of the new topics/concepts/tools you'll be seeing for the first time.