The linked article lists a lot of jobs that a frontend developer may be asked to do. Many sites certainly have all of those, but it is not realistic to say that

The linked article lists a lot of jobs that a frontend developer may be asked to do. Many sites certainly have all of those, but it is not realistic to say that every frontend developer is expected to know how to do all of these. (honestly these days I'm happy if a frontend developer actually knows what a DOM node is). But it is certainly true that Frontend development is complicated, and often under-appreciated. IME, the person doing a final integration is always the person who has to deal with all the miscommunication that has accumulated over the project. This is true in all fields I am aware of. Frontend development typically fills this role, because the flaws in the design of the data layer, or the miscommunications between the business stakeholder and the designer are typically invisible until someone actually tries to integrate it end to end. Actually delivering a good user experience in a reasonable amount of time while identifying and mitigating these hurdles is very challenging, and can be taken for granted especially if you end up doing a good job at it. IME the items listed in the article do happen to some people some times, but are much less fundamental than the general integration problem.