> To me, the main reason is different: You won’t be a master at frontend development if you don’t understand underlying mechanisms of a language.
True for any paradigm, not just frontend.
True for any paradigm, not just frontend.
Design have two aspects, the doing (drawing, documenting, adjusting) and the thinking (what’s the actual problem and the concept to solve it, which will give me a frame of choices). There is a lot of content on solving the right problem - check the resources from IDEO, or for a broader view Don Norman for example https://www.amazon.com/Design-Everyday-Things-Revised-Expand...
Also don’t forget typography basics since most websites, apps and documents are mostly only text, there are lots of tutorials out there.
Think I got that in a fortune cookie once.