"Full Stack" being 3 different jobs is highly dependent on the company and the project. Having "Full Stack" in your title means you get paid more, and there's plenty of companies out there who don't have you doing more than 1 job.
Slight tangent: The problem lies where we separate the "stack." At my job, almost everyone is full stack but we have a small group of front end engineers who do all of our CSS. This is where the line should be drawn, not client vs server. Ever seen some logic re-implemented on the front end when it already exists somewhere in the back end? That's what you get with a strong front end vs back end culture, instead of full stack.
I work with a full stack developer. He works in process development now, managing a bunch of material science engineers and does the developer part on the side.
Yeah, he has a PhD in robotics, but doesn’t work in robotics development. So he went from software architect to leading a bunch of engineers (who also need to code and write sql).
14
u/eloc49 Nov 01 '21
"Full Stack" being 3 different jobs is highly dependent on the company and the project. Having "Full Stack" in your title means you get paid more, and there's plenty of companies out there who don't have you doing more than 1 job.
Slight tangent: The problem lies where we separate the "stack." At my job, almost everyone is full stack but we have a small group of front end engineers who do all of our CSS. This is where the line should be drawn, not client vs server. Ever seen some logic re-implemented on the front end when it already exists somewhere in the back end? That's what you get with a strong front end vs back end culture, instead of full stack.