Actually, having started as full stack (including hardware, telephone and networking solutions), in hindsight I accept that while there are full stack developers, you could also call them "developers without specialization".
That doesn't mean they are not as good (some may be even better for their more diverse perspective), merely less specialized in their field than front or back end developers.
Thus, it depends on what the task is. In some cases, the specialization will be a real benefit, in others it could be helpful to develop the whole with both sides in one mind.
Especially smaller projects benefit from going full stack, whereas larger teams profit more from specialization.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Actually, having started as full stack (including hardware, telephone and networking solutions), in hindsight I accept that while there are full stack developers, you could also call them "developers without specialization".
That doesn't mean they are not as good (some may be even better for their more diverse perspective), merely less specialized in their field than front or back end developers.
Thus, it depends on what the task is. In some cases, the specialization will be a real benefit, in others it could be helpful to develop the whole with both sides in one mind.
Especially smaller projects benefit from going full stack, whereas larger teams profit more from specialization.