Isolation is the problem, and front-end vs. back-end is the same battle that waged in coding vs. administration. From that battle emerged the concept of DevOps, where things unified, and developers contribute to multiple components.
I see the same thing happen with front-end vs. back-end. If we consider this a protocol split, like a front-end may only talk JSON with the back-end, then a front-end developer will be severely stunted in their abilities. Creating UI's often requires changing how the back-end works. It's counterproductive to require a continual back-and-forth with other developers on every minutiae.
Being labelled front-end would imply your focus is on the UI, the most immediate part of the user experience. You will be the foremost authority when it comes to technical matters in code relating to the front-end. To somehow say this limits the code you touch, is counter-productive.
In all roles where I've worked on front-end, I've always touched code on the server as well. There's no way I'd be able to build the UIs I want without being able to do that.
That's really interesting, I like to hear what other people's experiences are. I've talked to various different frontend devs who have a variety of different ideas of what their job role is.
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.
Isolation is the problem, and front-end vs. back-end is the same battle that waged in coding vs. administration. From that battle emerged the concept of DevOps, where things unified, and developers contribute to multiple components.
I see the same thing happen with front-end vs. back-end. If we consider this a protocol split, like a front-end may only talk JSON with the back-end, then a front-end developer will be severely stunted in their abilities. Creating UI's often requires changing how the back-end works. It's counterproductive to require a continual back-and-forth with other developers on every minutiae.
Being labelled front-end would imply your focus is on the UI, the most immediate part of the user experience. You will be the foremost authority when it comes to technical matters in code relating to the front-end. To somehow say this limits the code you touch, is counter-productive.
In all roles where I've worked on front-end, I've always touched code on the server as well. There's no way I'd be able to build the UIs I want without being able to do that.
That's really interesting, I like to hear what other people's experiences are. I've talked to various different frontend devs who have a variety of different ideas of what their job role is.