>The two are very different roles which can rarely be fulfilled by a single person. I think we should stop trying to bundle them into the same thing. I don't k

>The two are very different roles which can rarely be fulfilled by a single person. I think we should stop trying to bundle them into the same thing. I don't know if this is universally true. While there may be some cases where splitting up the the visual elements from the API calls is necessary for a company/team, I don't think it's common. The problem with that division is that while it may make the scope of development smaller for each developer, it makes the process of implementing features harder. Unless you work on some monolith service that handles hundreds of UI changes and has an (overly) complicated backend API, or you are super short on devs, I'm not sure it makes sense to dedicate one person fully the role of 'html/css/js dev' and 'front end api dev'. CSS/HTML/JS animations/interactions are pretty trivial to implement. The bulk of being a 'front end developer' is getting the visual components to talk to the backend-api. Furthermore, I think the more we (as a community) define this developer roles into sub-roles, we ourselves a disservice. It makes the recruiting landscape more hellish (no 'front-end api developer' title on your resume? Guess you won't get past the robots even with 10 years fullstack experience).