I feel like you forgot to mention that if you want to be good frontend developer you should have some basic knowledge of tech stack that your closest coworkers use. You've mentioned databases and APIs but being familiar with design/ux basics is just as important. Employers don't need a code monkey but someone who is able to actively discuss and question decissions and that should apply to your coworkers as well. It's much harder to work with designer that doesn't think about resposivenes/accessibility or doesn't know the difference between dropdown and select.
I understand your point but Frontend is not designing. So you don't need to start learning the principles of UX-UI and design systems, and graphic design and typography essentials unless you're the designer and also the frontend of your company. Which... Actually shouldn't ever happen.
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.
I feel like you forgot to mention that if you want to be good frontend developer you should have some basic knowledge of tech stack that your closest coworkers use. You've mentioned databases and APIs but being familiar with design/ux basics is just as important. Employers don't need a code monkey but someone who is able to actively discuss and question decissions and that should apply to your coworkers as well. It's much harder to work with designer that doesn't think about resposivenes/accessibility or doesn't know the difference between dropdown and select.
I understand your point but Frontend is not designing. So you don't need to start learning the principles of UX-UI and design systems, and graphic design and typography essentials unless you're the designer and also the frontend of your company. Which... Actually shouldn't ever happen.
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!