I would say the biggest thing starting out is trying not to get discouraged as things start to get tougher. It can be very easy to get frustrated and hopeless when you start to encounter situations where you just have no idea what to do, or can't figure out why your code isn't working. This is normal, and it happens to everyone at one point or another.
Even industry figureheads like Dan Abramov don't know everything, and you will inevitably run into situations where you are delving into unfamiliar territory, and it feels like you'll never find the answer. This is normal, and with time (and repetition) these things you're having trouble with will only help expand your repertoire as you move toward certain mastery. You just need to persevere.
The other thing I'll mention is, make sure you're always building. It can be tempting (and I still fall prey to this, at times) to just focus strictly on learning materials like online courses, textbooks, lecture or tutorial videos, etc. It feels like you're making progress, and you're learning. But the way you will master those skills is by actually applying them. So even if it's something small, go and build some project using the new thing you've learned. Always be practically applying what you're learning, rather than just "learning" it and assuming it will stay in your head.
To avoid burnout, it might be worth looking into the Pomodoro Technique. It helps make sure you're getting proper breaks, and not forgetting to relax and reflect on what you've learned as you go along. Here's a helpful timer for this purpose.
If you have any questions you need help with, or you want to chat at any point, please don't hesitate to reach out to me.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would say the biggest thing starting out is trying not to get discouraged as things start to get tougher. It can be very easy to get frustrated and hopeless when you start to encounter situations where you just have no idea what to do, or can't figure out why your code isn't working. This is normal, and it happens to everyone at one point or another.
Even industry figureheads like Dan Abramov don't know everything, and you will inevitably run into situations where you are delving into unfamiliar territory, and it feels like you'll never find the answer. This is normal, and with time (and repetition) these things you're having trouble with will only help expand your repertoire as you move toward certain mastery. You just need to persevere.
The other thing I'll mention is, make sure you're always building. It can be tempting (and I still fall prey to this, at times) to just focus strictly on learning materials like online courses, textbooks, lecture or tutorial videos, etc. It feels like you're making progress, and you're learning. But the way you will master those skills is by actually applying them. So even if it's something small, go and build some project using the new thing you've learned. Always be practically applying what you're learning, rather than just "learning" it and assuming it will stay in your head.
To avoid burnout, it might be worth looking into the Pomodoro Technique. It helps make sure you're getting proper breaks, and not forgetting to relax and reflect on what you've learned as you go along. Here's a helpful timer for this purpose.
If you have any questions you need help with, or you want to chat at any point, please don't hesitate to reach out to me.