Brad Frost's front-of-the-front-end / back-of-the-front-end split has found an audience, and there is a concrete reason: some clients have reportedly moved their hiring away from full-stack roles and toward these more specific categories. The distinction itself is deliberately simple.

A succinct way I’ve framed the split is that a front-of-the-front-end developer determines the look and feel of a button, while a back-of-the-front-end developer determines what happens when that button is clicked.

Where the line actually falls

The clarity is appealing, but the boundary is not as clean as the one-liner suggests. A developer can be firmly front-of-the-front by temperament and still spend the day handling click behavior — updating state and firing off a GraphQL mutation, for instance. Owning that onClick does not automatically push someone into back-of-the-front territory.

What separates the two is not the presence of a click handler but the depth of responsibility behind it. Standing up that GraphQL API, troubleshooting it, understanding the security implications of the network request, judging whether a query will be performant, or knowing where to look on a graph to find out — those are the capabilities that mark out the back side of the front end.

Fuzzy by design

Frost acknowledges the border is not fixed. In his words, the line "can be fuzzy and varies greatly from developer to developer," and a single developer may well perform tasks across the entire front-end spectrum. What is uncommon is for that breadth to be typical.

This is the core objection to "full-stack" as a label. Many developers hold skills on both sides of the divide, which makes "full-stack" feel accurate when the more honest description is cross-stack. Full-stack implies deep knowledge of everything across the front end and the back end alike. If that profile is uncommon, it is arguably rare.

The larger regret about dividing front-end development in half is that a two-part split is too tidy a metaphor for a messy discipline. A local analogy: in a town where outdoor hobbies dominate, nobody asks whether you are a summer sports person or a winter sports person, because most people are both — but the specific mix differs. One person snowshoes, skis downhill, and day hikes; the next paddle boards, nordic skis, and mountain bikes.

Front-end skills resist collapsing into a single side for the same reason. The more useful model is a personal list: HTML, CSS, JavaScript, build processes, design, React, WordPress, plus a dash of accessibility, performance, and copywriting. The question of what that combination makes you has no category answer — it makes you you.