DEV Community

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

Collapse
 
diguifi profile image
Diego Penha

I like your post, but there's two things that suck about full stack and it's very important to mention, before telling people to go this path.
1 - It's a cheap way for companies to explore your job to the maximum, spending the minimum amount of money. You don't get paid as "front + back" dev (as it should, since you do both), you get a single salary that corresponds to "full". Good for them, bad for you.

2 - The chance is that people will start to become worse at specifics of front or back, people will have average knowlege, and thus, create average quality apps. It's important that full back and full front devs still exist, because focusing on a single stack makes it much feasible to be actually GOOD at what you do.

So if you're reading this and planning on go full stack, becareful not to become a shallow dev, with median/average knowlege on each stack. Always look foward to deepen your studies on specifics of some stack, because this will make you different from the rest, and actually an useful and powerful dev among the masses. Also, remember that being a full stack is great for companies, but means a lot of work, with no extra money, for you.

Collapse
 
andrewbaisden profile image
Andrew Baisden

There is a caveat here and that is freelancing. If you are freelancing as a full-stack developer then you can afford to charge more because you don't need to outsource part of the work.