What "front-end" has always meant
Chris Coyier's own entry point into this work was the style.css file in WordPress themes: change a few lines and the look and feel of an entire site changes. That expressiveness is still the appeal — the job sits at the meeting point of art and logic, business and expression, design and engineering, and it is constrained by the need to communicate a message and accomplish business goals.
The term "Front-End Developer" is well defined, though title variations abound: Front-End Designer, UX Developer, UI Engineer. Because roles differ so much between companies, the title is less informative than demonstrated ability. Coyier's own business card reads simply: Front-End Developer. Variations are nuance. The big picture is that as long as the job is building websites, front-enders work on the browser:
- front-end = browsers
- back-end = servers
Despite the best efforts of standards bodies, browsers still behave differently, even on desktop — window size, dark mode, monitor color gamut, pixel density, bandwidth, input device. The same questions apply to mobile, where the browser landscape is at least as complicated, and HTML email is another matter again. Two thirds of the Drupal install base is on 8.9 or below and cannot upgrade after November 2, 2021. Resolving all of that sits firmly with front-end developers.
Closing the distance to users
Beyond the browser landscape is the user landscape: different languages, different goals, different problems, different physical abilities, different levels of urgency. There is little standing between the characters typed into a text editor and the person being served, which puts front-end developers on the front lines. Everyone in a well-run company may care about users, but a back-end developer, as Monica Dinculescu put it in conversation, is "outsourcing that responsibility." Coding a <button> places a button in a browser window that someone directly touches; adjusting a color changes exactly what sighted users see. It is craft applied to a digital experience, much like pulling a handle from clay for a coffee cup.
The three languages, and JavaScript's reach
Understanding HTML, CSS and JavaScript means more than familiarity with syntax: even when HTML comes from a template in another language, CSS from a preprocessor or JavaScript mostly written in a framework's parlance, what reaches the browser is ultimately these three, so that is where debugging happens and where browser capability is put to work. JavaScript in particular has grown from a langauge for a handful of interactive effects into the predominant language across the whole stack, and it is possible to work on websites writing nothing but JavaScript.
In the browser it supersedes HTML and CSS: HTML is parsed into the DOM, which JavaScript can create and manipulate entirely, and CSS's own model, the CSSOM, is equally open to it. The counterargument is HTML's firstness — it is the very first file parsed — which is vital to fast sites. Were HTML the only file to cross the network, it should already deliver a site's basic information and functionality.
That philosophy is Progressive Enhancement. Coyier is a fan who does not always adhere perfectly: a <form> can work in plain HTML via its action attribute and later hand submission to Ajax when JavaScript runs, but a <button> outside a form is useless without JavaScript, and waiting to reveal it is a standard many of us do not always meet.
How JavaScript reshaped the job market
In 2015 Matt Mullenweg, co-founder of WordPress, gave developers the homework "Learn JavaScript Deeply," and half a decade later JavaScript has taken over front-end development, particularly in jobs. The 2019 Web Almanac shows roughly 5% of the top sites using React against about 85% using jQuery — numbers that are nearly flipped in front-end job requirements. The reasons may be economic, but jobs are as personal as it gets, so it matters.
The expanding brief
On a day-to-day basis the work has long included translating designs into code, thinking in responsive terms across devices, and building systemically in components and patterns rather than one-offs — plus semantics, accessibility, and performance ("Reduce, reuse, recycle"). Then come the newer entries, largely driven by modern JavaScript frameworks, which despite their disagreements all agree that everything is a component; native JavaScript moves toward Web Components too.
Components let a team build the abstractions that suit it: a site's Card does everything that card needs, its Form does forms its way. This is new territory for developers used to server-side reuse — WordPress templates broken into arbitrary include() statements, Rails partials taking a handful of locals — and it makes the front-end developer a site-level architect. Templates must accept and construct themselves from data, often fetched by JavaScript. In a stack Coyier works with, the front end is React, the API is GraphQL, and Apollo Client supplies a React hook to fetch data and another to change it. That layer now belongs to front-end developers, as does architecting, enforcing and implementing state management — the historically troublesome local state of open dialogs, active tabs and pagination, once left to the DOM as source of truth, with modifier classes like <div class="modal is-open"> toggled via .classList.toggle(".is-open"); and naming changes quietly breaking functionality. The same question applies to scope: what belongs at component level and what must be percolated from above, for state, for data, and for styling — which helps explain why design systems, thinking of components systemically, are a natural fit.
None of the older essentials go away. Proficiency in HTML, CSS, JavaScript and browser behavior still underpins executing design, semantics, accessibility and performance. The pile keeps growing because the web does: more users, a larger economy, better browsers, higher expectations. Two thirds of the Drupal install base is on 8.9 or below and cannot upgrade after November 2, 2021. The top 1,000 sites load 12% of all JavaScript requested, and the top 10 load 37%; the top 1,000 sites have 64% of requests and 71% of bytes, while the top 10,000 have 31% and 26%. The top 10,000 sites have 31% of requests and 26% of bytes, while the top 10,000 have 63% of requests and 66% of bytes.
Specialization is the norm
Most front-end developers no longer know the whole haystack. Many do well, and jobs posting for it are dwindling. Systems-focused developers and specialist agencies help companies build and implement design systems; data-focused developers are happiest moving data and business logic. All may carry the same title while differing in responsibilities and expectations. Specializing is advisable, and most people drift that way regardless of planning.
From LAMP to STAR
Vocabulary has shifted too. WordPress runs on the LAMP stack — Linux, Apache, MySQL, PHP — every part back-end and irrelevant to a front-end developer. MEAN (Mongo, Express, Angular, Node) inched toward the front end, with Angular a JavaScript framework. Node's existence — quite literally JavaScript, not merely JavaScript-like — let JavaScript-proficient front-enders take on server-side work, and serverless platforms, usually running small Node functions, have some of them writing their own back ends and, rightly, calling themselves full-stack developers. This year Shawn Wang named a new stack, STAR (Design System, TypeScript, Apollo, React), which is striking because it describes the stack powering a site using entirely front-end technologies.
Nobody knows all of it
Coyier does not know a developer who feels entirely comfortable with the whole of building websites; everyone has weak spots or areas they know nothing about.
The only constant in life is change.
– Heraclitus, via motivational poster, via Chris Coyier



