1. Decide on a non-trivial project. It doesn't matter what, but it should interest you at least a bit. It shouldn't be enormous ideally, but ultimately too big

1. Decide on a non-trivial project. It doesn't matter what, but it should interest you at least a bit. It shouldn't be enormous ideally, but ultimately too big is better than too small. 2. Decide on the tech stack. It doesn't matter if your decision is not the best. There are no bad decisions. Stick to that stack for that project, no matter what. 3. Start breaking down the project to small steps, and start reading your stack's documentation like crazy, and googling your current step "how to display cats with SQL" or whatever. Implement that step. 4. Keep repeating step 3 until your project is done. This is the most important: don't stop until you finish. 5. Once you finish, you have learned a lot. It is time to reflect why SQL wasn't the most ideal choice to build a music player's frontend. (Also, it is time to reflect on how many other people could do the same). Don't learn blindly from random youtube videos. Learn by doing.