The Front-End Title Holds, But the Role Is Splitting
Benjamin De Cock recently tweeted that the title “Front-End Developer” is obsolete. I wouldn’t go that far. The term’s strength is that “Front-End” literally means the browser, and the job — despite all its changes — is still about browser work. We’re browser people.
Still, his sentiment hits a real nerve. Too many web implementations are both heavier and worse because they re-implement what the browser already offers for free: scrolling behavior, snap points, fixed/sticky positioning, form controls, animation, and more.
Our industry seems to have acknowledged that backend and frontend developers require very different skills (even though they often use the exact same language), and yet it’s struggling to see there’s too much bundled into the term “front-end developer”.
That’s the heart of the matter, and it’s exactly what “The Great Divide” has been about. A huge share of front-end developers work almost exclusively in JavaScript. Calling them “JavaScript Engineers” or “JavaScript Developers” fits fine. But it’s unclear what label to stick on someone who is a strong front-end developer, not especially JS-focused, and works across the other facets of the front end.
The modern frontend developer is most often than not a “Jack of all trades” mastering JS (or even just a framework) and barely tolerating HTML/CSS as a necessary evil. That’s understandable. I strongly think it’s a different specialization, and it’s too much for a single person.
That divide is not a problem; it’s just reality. Front-end teams need JavaScript specialists, CSS specialists, accessibility specialists, performance specialists, animation specialists, and internationalization specialists. None of these need to be separate roles — people can be strong in more than one area. But it’s rare to find someone who excels at everything, even with the scope limited strictly to front-end skills.
