Recently, I see a few articles and people talking about “too much CSS”. Are we at the point where we will have »CSS Engineer« or »CSS Developer« positions on the job market? It would make sense and clarify things compared to »Frontend Engineer«.
There are 548 properties in the CSS spec. 🤯
How can we practically learn when and how to use all this? —Cory House on Twitter
Back in the times…
But it was also a very limited web. We didn’t have
vw), and styling methods (shadows, transforms, border-styles). Over the years, we got more and more possibilities to create great websites. With that, people started to divide into infrastructure, backend- and frontend developers.
We live here, now.
Nowadays things are very different. But before we get into more details we have to divide this into two categories: Small websites for normal companies or people and big web services that drive a whole company or software system. And here’s where the clue lies:
For small websites, we need engineers who can code the whole frontend or maybe even do everything on their own, the full stack.
»CSS evolved and we’re beyond the point where everyone can just do it as a side interest.«
Vice-versa it’s not easy for people anymore to say they’re not great at coding React, Vue, or other frameworks, even if they excel in CSS. Having a job that’s tied to expertise makes sense to me. And since we already have job titles such as »React developer«, »Performance engineer« and others, »CSS engineer« would point out the requirements for the job as well as the strengths of the applicants to recruiters.
CSS evolved and we’re beyond the point where everyone can just do it as a side interest. We all can learn it and build amazing stuff with it, but using it wisely and correctly in a large-scale context isn’t an easy job anymore. It deserves people whose work is to focus on that part of the code.