Everyone has already mentioned great tips, find something that whets the whistle. Most large OSS projects now label a lot of their bugs with a 'beginner'/'get-started' tag. Start where your interests and that work collides, and work from there. If it doesn't float your boat, you learned something by trying, and find the next thing that intrigues you. Reddit is a better community now than SO, but SO does have a lot of answers. However, most large projects (epecially in JS) have gitter/slack/discord/irc/x groups that are either resolving issues, or answering questions, just be patient. Another way I've been also told is helping with documentation on certain projects as well if bandwidth doesn't permit code dives.

Eh, to each it's own. I get your point, and it's true, most use these for handicaps, but unfortunately no one ain't got time (especially business) to use raw fundamentals. So humans do what humans do... jump on hypetrains without any knowledge, and hope it all works out.

My issue starts with the comparison of a library (React) v. a framework. React+[MobX/Redux/RxJs/__]. Vue already has a lot of the application management ecosystem that React doesn't provide out the box. React is just a view handler with some limited local state management. At the end of the day it depends on time. If you need everything ready to go Vue, but if you have the time to tinker, React and __.

But react is a library... not a framework...

I got tired of fighting it/ languages got simpler. My pops is a computer technician so I've been around computers all my life. I was familiar with BASIC, DOS, and even Apple's original cli. But it was never enticing for me to get into it, plus no one knew what computers really were capable of outside of word processing, excel sheets, and being better than a typewriter. Most my childhood was just testing waters, and eventually not finding enough resources to commit when I got stuck. Fast forward, I ended up on the track of becoming an Art Director. I was in a finishing school in San Fran and all my teachers hated their jobs, but loved their side hustles, and they were working with engineers from the big five. But when I saw what they were doing, I knew had to jump in (all were just simple sites that generated 1k clicks a day). It's the one job that encourages failure, pushes you to continuously learn, and rewards you for both. I hate it took so long, but I don't regret it.

It depends on your knowledge and time. I'd recommend ES6 for better understanding of JS (although TS can do the same). TS is a superset of ES_ so the argument is confusing. I'm guessing this is more so to do with if you want to have a strongly-typed environment versus standard js. If you have limited time TS, but for better understanding of your code (knowledge aspect) I'd recommend ES6. The syntactic sugar and type enforcement can be a hindrance in understanding the double edged sword that is Javascript. You also still could just write ES6 in TS and have both.

Definitely same. I'd love to be able to implement this strategy at a much earlier stage, but unfortunately my boss isn't too familiar with react thinking so as time progresses move to this structure but initially nope... well at least a work.

I wavers between this site called brain.fm that creates these sounds to promote cognitive effects (focus, relax, sleep). Other than that the Lofi channels on YT have a pretty good balance of mid to uptempo tracks with minimal vocals.