DEV Community

Discussion on: Why you should become a Full-Stack Developer

Collapse
dastasoft profile image
dastasoft

I agree with you but I don't particularly like the statement "go down the Full-Stack path as quickly as you can" I understand your point but having a good base is also important, maybe the nuance is that they start with front-end or back-end whichever they like the most but when they reach a certain level they are not afraid to "jump" to the other specialization.

It's fine to dive into front-end if you are back-end or vice versa, even if you still have a lot to learn in your field, but I think it's important to have a solid foundation in at least one of the two.

But in general I agree that jumping to full stack is valuable, especially for the person who will be able to make a whole application by himself.

Collapse
andrewbaisden profile image
Andrew Baisden Author • Edited

In my experience I regret not looking into back-end earlier I was so stuck on only using the front-end and staying oblivious to anything back-end. I missed out on so many jobs because they wanted someone who knew the basics of SQL even though it was a front-end role and I refused to even think about looking at SQL back then.

I also thought that databases and servers were hard, too technically confusing and out of my scope. Now it just feels natural working on the back-end and switching to the front-end.

Collapse
dastasoft profile image
dastasoft

Yes, absolutely, I think the key point here is to know the sweet spot for making that jump, but as you're pointing out it's healthy to stay curious about the other field and try to at least get an overview of what's out there and what you need.

Maybe it's a bit easier to go from a back-end job to trying things out on your own in front-end than vice versa, because back-end without any previous experience seems like a black box full of magic. For front-ends SQL is one of the main concerns and for back-ends I think it's CSS :D