Ooo that’s a great question. I think you can already see the divisions (or subdivisions) along the line that stretches between the design and look and feel side of UI to the mechanics of it all (i.e. the JavaScript).
Also, there are people who love to work in the front end side of things but just aren’t design inclined, so would prefer to hand those parts to a dedicated person or team.
But the lines are already very blurry and the terms ‘backend’ and ‘front end’ feel a little loose to me. It feels like we talk a lot more around being a developer first and then which tech stack matches your skill set most closely. And there are people who specialise and niche off into day, accessibility or CSS or performance optimisation.
In the end, I think there will always exist a large Venn diagram between design and development and it doesn’t hurt for either side to dabble in the middle a little. It’s better for them, better for the team, and ultimately better for the user.
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.
Ooo that’s a great question. I think you can already see the divisions (or subdivisions) along the line that stretches between the design and look and feel side of UI to the mechanics of it all (i.e. the JavaScript).
Also, there are people who love to work in the front end side of things but just aren’t design inclined, so would prefer to hand those parts to a dedicated person or team.
But the lines are already very blurry and the terms ‘backend’ and ‘front end’ feel a little loose to me. It feels like we talk a lot more around being a developer first and then which tech stack matches your skill set most closely. And there are people who specialise and niche off into day, accessibility or CSS or performance optimisation.
In the end, I think there will always exist a large Venn diagram between design and development and it doesn’t hurt for either side to dabble in the middle a little. It’s better for them, better for the team, and ultimately better for the user.