Summary:

What's full-stack development - how do the complexities of front-end and back-end compare?

This article delves into the nuances of full-stack development, highlighting the challenges and misconceptions that arise from different areas of expertise within the field.

The author, Elly, redefines their identity as a "front-of-the-front-end developer" and ultimately settles on the simple title of "web designer."

Main Arguments:

• Recognizing and valuing specialized skills in areas like accessibility, design systems, and design is important.

• There seems to be a pressure to conform to labels such as "full-stack developer," despite specialized skills in front-end or back-end development.

• Is there a JavaScript-industrial complex for blurring the lines between front-end and back-end responsibilities?

• Does the blurring of lines result in a lack of expertise in essential areas such as CSS and design systems?

Notable quotes:

HTML, CSS, JavaScript, Python, C#, and SQL may all be code, but they’re really quite different kinds of code and are suited to different kinds of people.

Just because I know how to use Docker, Node.js, PHP, SQL, AWS, Linux, Serverless... doesn’t mean I actually produce quality work in any of those things.

The value you want from a CSS expert is their CSS, not their JavaScript, so it’s absurd to make JavaScript a requirement.

Conclusion:

The article challenges the prevailing norms in the tech industry by advocating for a reevaluation of job titles and a reemphasis on specialized skills within web development. By highlighting the importance of clear distinctions between roles and the value of expertise in specific areas, the author calls for a more nuanced understanding of the diverse skills required in the field.

References and Additional Resources:

• Full stack developers

• The great divide

• Why your web design sucks