I concur with all the above experiences and advice.
I find it much easier to write code (development logic) rather than design (CSS, PSD, graphics, etc).
Going through the FCC course, the most challenging aspect for me has been CSS (or rather good CSS) (I know, CSS is supposed to be easier than JavaScript, but I find it tougher). Getting code right (and good) seems to take fewer tries than gettinig whatever I am working on to look good. The CSS and design part seem to take 80% of the time I spend on a project.
And unfortunately as humans, we tend to judge books by their covers (including other areas of life). So even though under the hood stuff is awesome, performant, elegant, etc. people don’t really notice it and base their judgement on how it looks on the outside - i.e. fancy graphics, animations, javascript widgets, etc.
The only thing I can suggest, as others have, is to treat it as 2 different skill sets - i.e. are you a designer or developer? (If you put in enough time into both, then you’d probably become a good Developer and Designer. In my experience of interacting with software professionals (online and offline), I have found relatively few people that are both.
Before beginning FCC, I had always thought backend and pure development work was harder and front-end stuff was easier. I was SO WRONG! Being a good front-end developer is quite challenging and has its own unique challenges.
The other thing I would suggest is not to worry about things being bad in the beginning. Very few things in life are perfect on the first go. Why should designing things be any different?
As you (we FCC campers) spend more time and get more practice with the skills we are weak at, we too will someday hopefully look back and marvel at the journey from beginner to accomplished.