> understanding the tradeoffs is usually the hardest part This feels especially true in the front-end. Whenever I try to learn new things I always try to find

> understanding the tradeoffs is usually the hardest part This feels especially true in the front-end. Whenever I try to learn new things I always try to find the online communities, the main books, the podcasts, etc. I try to find the people down to bikeshed about something most wouldn't care about. I feel like this learning strategy has been especially effective in the front-end world. If you start a new job, chances are you're gonna have a huge chunk of your stack be totally new just because of how many solutions there are for everything out there. I feel like the main value-add I bring a lot of times is just knowing what's out there and what the best tool for the job is. Most of the time I haven't actually used that tool The hard part is cutting through the bs and knowing what's hyped because of a certain interest group and what's hyped because it's an actual improvement. For that, I find you usually do need to have some hands on experience