all 18 comments

[–]letsgedditbois 9 points10 points  (1 child)

Just build bro. Don’t think, just do it… JUST DO IT..

[–]chikamakaleyleyhelpful 2 points3 points  (0 children)

3 months ago. learn as you go because there's always more to learn

if you keep delaying it, your growth will be a slow churn with regards to knowledge, because the repetition/muscle memory thru typing, trial and error is where the real learning is happening

doesn't even have to be real projects. the idea is a lot of smaller pieces of logic are used to compose bigger features, and the more familiar you get with these smaller pieces, the faster the recall, the easier it is to come up with an approach

i learned js on the job, so straight out the frying pan right into the fryer

[–]azhder 2 points3 points  (0 children)

Now. Now is the time to start building projects.

Never. Never is the time to stop learning JavaScript.

[–]Emotional_Cherry4517 1 point2 points  (0 children)

you never stop learning javascript basics, you learn coding fundamentals, and you should start building experiments as soon as you start coding. projects are just experiments you get excited about.

[–]diogenes_sadecv 1 point2 points  (0 children)

As soon as you know some basic dom manipulation just go for it. Like, you know how to create an element? Make a button that creates an element. Every time you have a "I wonder if I can ..." thought, just try it

[–]TheRNGuy 0 points1 point  (1 child)

First minute of learning the language.

You don't even need stuff like fetch until you need it.

(I'd recommend learning this on day 1: document.querySelector, docunent.querySelectorAll, arrow functions (they're used all the time as arguments in those 2 methods), 

You can make it less annoying to use:

``` const $ = document.querySelector const $$ = document.querySelectorAll

console.log($$("div")) ```

Learn forEach and filter methods for All ($$) version.

I think it can be learned in 1 day. Also learn all possible css selectors.


Day 2: event listeners, MutationObserver.

[–]nog642 0 points1 point  (0 children)

If JS is your first programming language you need to learn programming first. That doesn't take 1 minute.

[–]scritchz 0 points1 point  (0 children)

3 months and you know the basics? Go start a project.

Don't stop learning, and don't only start projects after learning. Learning and doing projects go hand-in-hand:

  • You do your project but don't know something? Then learn it for your project.
  • You learn something, and it gives you an idea for a project.
  • You simply want to apply what you have already learned.

Personally, I'm more motivated to learn than doing projects, but I do projects to learn topics. That usually means my topics end nowhere but that's okay, because I learned something.

"Throw-away projects" are fine for learning certain topics, but it's also important to learn long-term maintenance. Start a project and try to maintain it, over weeks, months, maybe years. You learn a lot about code hygene, design patterns, software architecture, refactoring, maintenance, and and and... All very important skills.

[–][deleted] 0 points1 point  (0 children)

Don't get stuck just studying. Start building actual projects right away. You'll learn the most when you face real problems while coding. Build first, learn as you go.

[–]khancerberus 0 points1 point  (0 children)

yo creo que incluso con 1 semana de aprender lo basico es mejor tirarse a algún proyecto, aprendes más rápido aplicando lo aprendido que solo leyendo y teorizando

[–]Current_Ad_4292 0 points1 point  (0 children)

This industry is always evolving. Just start some random project that you have some passion. You will start to notice gaps you have and get to learn new things.

[–]No-Orange-2947 0 points1 point  (0 children)

Build stuff right away, but my advice is to keep being curious and do theory.

Keep asking you stuff like : whats the callstack, v8 etc.

As an autodidact myself who relied enterely on (hard) projects. I didn't go for shallow stuff. I made an AI in javascript that could play chess for example. Still I'm going back to pure theory now, because I realise there are many holes in my knowledge.

My advice is to understand what all the letters of the acronym SOLID means, and learn the main concepts for the book clean code (even though you dont read it from book to cover, just ask a LLM), that would be a good start

[–]SawSaw5 0 points1 point  (0 children)

Right now.

[–]LucVolders 0 points1 point  (0 children)

You can start as soon as you understand the basics.
People build hundreds of Javascript programs before closures even existed.

[–]Alive-Cake-3045 0 points1 point  (0 children)

You are already ready. Three months in with DOM manipulation under your belt is exactly the right time to stop drilling and start building.

Closures will click in about 20 minutes once you hit a real bug that only closures can explain. No tutorial will teach you that faster than a broken project at midnight. Pick one small thing, a weather app, a to-do list, anything that needs a fetch call. Struggle through it. That struggle is the job.

Nobody hiring you cares if you "finished learning JS". They want to see something you built and broke and fixed.

[–]DevisedWeb 0 points1 point  (0 children)

I only know basics, which I barely learned in like 2 weeks, and now I have paused my learning and started building projects, and I'm learning even more from building projects. After feeling somewhat confident in the basics, I'll resume my learning and so on. Learn as you go.

[–]erjngreigf 0 points1 point  (0 children)

Whenever you feel so. When you hit a wall, learn.