It's not about being able to do work of designers/devops/backenders but about being able to understand what they are doing and discuss decissions on their side that affect you as well. You start this blog post saying that you are just a designer that codes. You are still a designer but much more valuable one because you have knowledge about frontend ecosystem and frameworks. And that's a big advantage against other designers that may have no idea how html or js works.
Maroš I really understand your point, it is good to have some knowledge but I often see the "design knowledge" that is being asked to frontenders is just too much and I don't think they'd use it in a company, but in their personal projects. Also, my developers discuss design things with me without knowing a lot of design 😆, the only thing you need it's being interested in your coworker's work, that's it!
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It's not about being able to do work of designers/devops/backenders but about being able to understand what they are doing and discuss decissions on their side that affect you as well. You start this blog post saying that you are just a designer that codes. You are still a designer but much more valuable one because you have knowledge about frontend ecosystem and frameworks. And that's a big advantage against other designers that may have no idea how html or js works.
Maroš I really understand your point, it is good to have some knowledge but I often see the "design knowledge" that is being asked to frontenders is just too much and I don't think they'd use it in a company, but in their personal projects. Also, my developers discuss design things with me without knowing a lot of design 😆, the only thing you need it's being interested in your coworker's work, that's it!