The Widening Responsibility for Front-End Developers | CSS-Tricks
This is an extended version of my essay “When front-end means full-stack” which was published in the wonderful Increment magazine put out by Stripe. It’s also something of an evolution of a couple other of my essays, “The Great Divide” and “Ooops, I guess we’re full-stack developers now.”
Vanilla JavaScript and HTML - No frameworks. No libraries. No problem.
Do you know what it takes to render HTML elements on a web page without Angular, React, Svelte, and Vue? Let's explore a controlled scenario of creating a simple web page and bring to the foreground what it takes to render a page with pure HTML, CSS, and JavaScript.
Let’s talk about the ternary operator. It can be confusing for many. In this video, Tonya puts the if/else side-by-side with its equivalent ternary to help you know and understand it. The alternate syntax tip is found here. This tip is valid for JavaScript and PHP.
Heydon Pickering published a fantastic post called Reluctant Gatekeeping: The Problem With Full Stack. I have about 3 blog post drafts covering similar ground and apparently we see very much eye-to-eye on this, so I thought it might be worthwhile to walk through Heydon’s post and layer on my comment
Is front-end development having an identity crisis?
Does front-end development as a we know it still exist; or has the role evolved into something we no longer recognise? As with evolution in nature, the evolution of "front-end" has resulted in several distinct flavours --- and in my opinion --- an identity crisis.