Back in the day we just had "webmaster", but splintered into at least UI/UX designer, content designer, front-end/back-end/full stack developer. I think that reflects the increasing complexity of the applications, likely a result of increased adoption of the internet.
But that's the nice thing about the internet. I can still put a simple HTML page out there and it'll work. Complexity is up to the author. But because of the optional complexity, it makes for a more difficult task to define the role of "web developer".
From the front-end-perspective, it's not sufficient anymore to do HTML & CSS only.
Javascript is essential—sometimes even for junior-positions.
This makes it increasingly harder for front-end-devs coming from a design-background, without any significant CS-knowledge.
I find this unfortunate, because developing web-interfaces and layouts (typography, motion etc.) needs a strong design-foundation, which more technical people often lack.
Top comments (3)
Back in the day we just had "webmaster", but splintered into at least UI/UX designer, content designer, front-end/back-end/full stack developer. I think that reflects the increasing complexity of the applications, likely a result of increased adoption of the internet.
But that's the nice thing about the internet. I can still put a simple HTML page out there and it'll work. Complexity is up to the author. But because of the optional complexity, it makes for a more difficult task to define the role of "web developer".
From the front-end-perspective, it's not sufficient anymore to do HTML & CSS only.
Javascript is essential—sometimes even for junior-positions.
This makes it increasingly harder for front-end-devs coming from a design-background, without any significant CS-knowledge.
I find this unfortunate, because developing web-interfaces and layouts (typography, motion etc.) needs a strong design-foundation, which more technical people often lack.
It went from something nearly meaningless, to something something worse than meaningless.