> I'm overwhelmed quickly when i have to solve a (simple) problem with javascript, so i think backend would not be an option. The truth though is JavaScript is

> I'm overwhelmed quickly when i have to solve a (simple) problem with javascript, so i think backend would not be an option. The truth though is JavaScript is a hard programming language. It has different environments like the browser and node. It has these specialized language transformations like babel that let you do different things based on experimental ES proposals. How do you measure competency as a programmer? I've done very intricate stuff around CMake and tested stuff to run from source on multiple OS. I've contributed to a diverse array of open source projects across many programming languages and platforms. Despite all that - webpack/babel/node's behavior boggles my mind. I question my competency routinely and look back and am confused at how I written such bad code. Even though at the moment I felt accomplished and think I've finally wrote something "future proof" and in good form. It's okay to give yourself more time, if you're willing to. Frontend programming is so hard and moves so fast. There's no such thing as mastering it since every 6 months there's a leap in toolchain / libraries / etc. If you are willing to grind it out, I've come to love TypeScript and React w/ hooks and find it scales very well on large projects. It is possible to get into a flow with webpack and co. if you can give it time.