Skip to content
loading...

re: Next phase of separation of job titles in web development VIEW POST

FULL DISCUSSION
 

Totally agree with this!

I am 100% a #1 (front-end designer) but it feels like if I'm not working towards #2 that my career will go nowhere (based on co-workers, industry types, etc.). Every "front-end" job posting in the last 2 years for "front-end" not only includes a requirement to have mastered HTML/CSS but the 4 latest JS frameworks as well.

If I'm not learning how to do CSS in JS I'm "behind the times" but if a JS dev doesn't truly understand CSS grids it doesn't seem like the industry treats that as much of a big deal.

Both of my statements are exaggerated as everyone is in unique situations but I'm glad to find articles and opinions that mesh with mine. 🙌

 
 

To put you at ease, you are not the only one. I thought so as well for a long time and it has become increasingly difficult to continue forward with JS because this is not what I want to do. That is "back-end stuff" and as a designer I don't see anything creative there. Somehow that programming part creeped in and now it is expected from us, web designers and front-end designers, to perform tasks that are more suited for pure programmers - JavaScript developers.

I will post a quote here from Brad Frost, creator of Atomic design. This is what inspired me to write this article.

Brad Frost

Source: smashingmagazine.com/atomic-design...

;)

code of conduct - report abuse