Rishi Chawda

Instead of writing a long piece of advice, I would first recommend you to go through this link: https://roadmap.sh/ This will give you a broad view of things you might need to check out for the frontend, backend, and DevOps too. Now for the second part of the question. Although you won't necessarily need to be very good with algorithms to land an entry-level job in a lot of companies, in order to become a good developer you MUST have a good grasp of algorithms. I cannot stress this enough - Any good developer knows how much it is important it is to understand different kinds of algorithms to optimize code while working with loads of data. You can probably check out this repo: https://github.com/trekhleb/javascript-algorithms for all JS implementations. For learning JS, you can read You Don't Know JS book: https://github.com/getify/You-Dont-Know-JS. Another resource for the concepts might be this: https://github.com/leonardomso/33-js-concepts Another place to find good blogs and all things development is dev.to.

I use React Native because it is a faster way to develop cross platform applications which provides a way to develop features consistently and in parallel. Being a Javascript developer with experience in React and a little mobile application development in Java ( for Android ), it was really easy for me to learn - which was basically understanding concepts specific to mobile development about which I knew a little already.

Personally, I never like installing too many applications / programs on my system. Even if it is a small one. For me, it is better to have aliases for commands and use them via terminal rather than having a program do that for me. Also, who needs aliases too if you're using Zsh autocompletion!

Thus when it came to developing a React Native application ( I started native mobile application development a few months ago ) -- I preferred using Google's Android Emulator rather than using third-party softwares that provide virtual devices to run the app. But also, I didn't want to install Android Studio which I'm never going to use anyways except for the emulator. So I ended up installing and using it through command line and also wrote a blog around it for #Mac , #Linux and #Windows users.

But after a few days, I started using USB Debugging with an external device whenever possible. Emulators just hog the device memory IMO.