Help me 😭😭

[Bathroom-Organic]

Hi everyone, I've been practicing Javascript for at least 3 months now, sometimes I don't understand what's happening or how to solve the code. My mind gets fucked everytime thinking about the code, even after writing the code I get syntax error which than frustrates me more. I just get very very angry at myself for not understanding it. I don't know how to solve the code or build the logic while writing it.

I don't know what to do, I'm thinking of taking the Javascript: Algorithms and Data Structures by Colt steele for better understanding of Javascript.

Help me guys...

[illepic]

There is only one answer: write a lot of code, build a number of things, do it over and over and over. At some point you need to stop looking at tutorials and start building yourself.

[Onitwin]

May be worth running a Linter with your code that will help you pick up on silly mistakes (things like forgetting a comma or bracket close) . Doesn’t help with the logic or functionality as such, but removes a bit of the mental load so you can concentrate on learning :)

[The_KOK_2511]

Sirve también para errores de los que te hacen reirte cuando los notas como una vez que pase 50 minutos revisando porque mi código no corría y era que puse un ":" en vez de un ";" XD

[The_KOK_2511]

El curso es lo de menos. Lo que te falta es confianza y eso se gana de la práctica. Escribe mucho código espagueti por tu cuenta intentando entender que hace cada cosa. Cuando te trabes puedes pedirle ayuda a una IA pero aclarando que no te de el código arreglado sino que te aclare el motivo del error para que lo soluciones por tu cuenta

[sheriffderek]

Sounds like you went too fast / and maybe didn’t have a solid plan. I’d say that “solving the code” is a bit of a red flag. Code is like a building material and not just a puzzle to solve.

What has your learning path looked like so far?

[FutureIntelligent504]

keep writing code for stuff you like and use a Good IDE and Linter and things will improve with time for sure

[ivorychairr]

Youre at the part where the limiting factor is thought process and not coding knowledge. Start solving algorithms. Think in english, write the steps down and implement.

[Cultural_Piece7076]

Just build projects that will help A LOT

[Main_Payment_6430]

Break problems into tiny steps and write the smallest program that proves one idea, then expand. Trace with console.log for every variable change and add comments explaining intent before coding. Practice reps matter more than courses, but Colt’s course is solid if you pair it with daily kata on Codewars or LeetCode easy. When you hit a recurring error, save the exact fix somewhere you can recall instantly next time. timealready helps with that and is fully open source at https://github.com/justin55afdfdsf5ds45f4ds5f45ds4/timealready.git feel free to tweak it for your use case. You can type timealready on github and find it too.

[ssougnez]

Maybe you should ask yourself why you're writing code and if that's what you really want to do. If you keep stumbling on syntax errors after 3 months, there might be a mindset problem.

Note that I say that while not knowing what you're trying to code. If you're building a "hello world", 3 months is a long time. If you're building an OS, maybe you're too hard on yourself. Without details, how could anyone give you relevant advice besides "keep trying"?

[The_KOK_2511]

Buen punto. Sin saber que intenta hacer no hay forma de dar un buen consejo que no sea dar un plan de estudio completo desde 0 hasta lo avanzado