Front-end development’s identity crisis
I'm a web designer
See ⮂ Also
The Great Divide Chris Coyier On one side, an army of developers whose interests, responsibilities, and skill sets are heavily revolved around JavaScript.
On the other, an army of developers whose interests, responsibilities, and skill sets are focused on other areas of the front end, like HTML, CSS, design, interaction, patterns, accessibility, etc.
Front-of-the-front-end and back-of-the-front-end web development Brad Frost 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 thatbutton
is clicked.We Need to Talk About the Front Web Angela Ricci The experience we have using the web deserves our attention; when the web loses, we lose too.
The front web is systematically undermined, and the main targets are precisely the aspects that make the web a powerful medium.
While these attacks are systematic, I'm not sure how conscious and intentional they are: are we never satisfied with what we have and we keep trying to improve it, or are we just “breaking things”?
Whether we are breaking things around or trying to improve the front web, what is clear to me is that instead of getting the most of it, we just keep making it heavy, inaccessible, unmanageable, and offering a very bad UX. It is hard to say who is benefiting from these attempts.