I think starting with the front-end path will keep me focused on one thing and help me secure a job or freelance opportunity, after which I can transition to the full-stack path. However, I don’t have enough experience to decide which one would be better.
1 Like
Welcome @AbdullahAshour !
Our Fullstack path is a more full on one but it’s recommended if you plan to dive into backend eventually. Some people are only interested in the Frontend components first so that’s recommended if you’re like that.
The Fullstack path is basically an extension of the Frontend path so you can really start on either but if you’re confident you’ll jump into backend, we recommend the Fullstack Path.
2 Likes
Really appreciate that, Roku! That makes things way clearer 
2 Likes
Then why do we have 2 path? Can’t we merge them together and make graduating once we complete frontend . And if someone wanna explore backend they can then move to backend or there are more frontend stuff on frontend course, which really isn’t needed for full stack path?
1 Like
That’s correct @sajwan05 . The Frontend Path includes content that’s more specifically focused on frontend development. We also have a Backend Path, which works in a similar way and contains additional content that isn’t part of the Fullstack Path.
It can be a bit confusing at first glance since there’s a lot of overlap between these paths. The idea, for now, is to keep them separate: the dedicated Frontend and Backend Paths are more comprehensive in their respective areas, while the Fullstack Path is designed to provide the quickest route to learning fullstack development. From there, students can decide whether they want to specialize further in frontend or backend and then dive into the corresponding path.
3 Likes
Okay got it, so after compleating full stack path if I feel like I’m more intrested in doing backend for example, so I can explore backend specific path.
It is confusing but alright, I got it.
3 Likes