Focus on the flow of your code, knowing perfect syntax is great but it's the tool we use to actually accomplish the thing we're trying to do and we've got tools and resources to help you master syntax later.
Algorithms are great, but you likely won't need to have therm all memorized when doing a job (an interview might be different). Learn what an algorithm is, practice implementing a few, learn the general idea of what a bunch of different algorithms can offer for different situations.
You'll always be able to look shit up on the job, but the less stuff you have to look up the more efficient you'll be.
Start and finish projects. Like fully finish, push something useful to npm or NuGet, stand up a website with a domain you control.
Don't just focus on one area at the start. Learn web stuff, but also at least one native language. Maybe get a microcontroller and set up a project where you can control something in the real world from a web interface.
Understand the use cases and differences of various languages and technologies. Why use go vs rust? Why use Java vs C#?
Learn the different styles of coding practices. Your codebase will be a mix of a bunch of different ones cause you'll end up writing what makes sense at the time, but knowing different styles will help you know what actually does make sense at different times
Avoid AI as you're learning. Your knowledge of code and it's underlying principals will allow you to understand when the AI is wrong--and it will be wrong. It's important to grow those fundamentals before reaching for a tool whose mistakes will be your responsibility.
Use Linux
I'd recommend using a high level OS like Debian or Fedora for a bit as you familiarize yourself with how to use Linux then try an arch install (not through any GUI) to learn how Linux actually operates.
1 Comments
unmagical@lemmy.ml · 1 pts · 3d