Javascript (The Odin Project workflow Questions)

Yes, I am a beginner when it comes to coding. Hi I am Juliane Figura, 17 Yrs. starting linux fundamentals, aswell as web dev from front to back end. My question is. How do I study or learn Javascript the right way? Because when ever I read the full documentation texts, I feel I wasn't learning anything, and I get stuck into one lesson, I feel I am so slow to programming, and my goal is to learn programming websites in just 8 months prior to my 2-3 hours coding after school. So I don't want to watch youtube tutorials because I wan't to improve my reading skills, and watching in youtube will lead me to tutorial hell. And addition in my learning, I am still in the Loops and Arrays, I've seen so much from the documentation sites such as MDN and JS.com, well I see those things like I don't undestand the things I see inside, so what I do is I go back to the completed lessons where I re read, and take notes. I feel my workflow is a mess, Can you recommend me a workflow based in your experience or maybe correct my workflow? thanks matsalove!

Comments

[Ali T]

Hi Juliane! First off, props to you for taking on web development and Linux fundamentals alongside school—that dedication will pay off big time.

Reading official documentation like MDN can definitely feel overwhelming when you're just starting out with Loops and Arrays, because MDN is written as a technical reference specification rather than a step-by-step tutorial. Reading docs is a great skill to build, but relying purely on reference docs without hands-on building is why you feel stuck.

Here is a practical, project-driven workflow designed for 2–3 hours of daily study:

1. The 30-20-50 Rule (For a 2-Hour Session)

• 30 mins - Read & Test: Read a single concept (e.g., Array loops or array methods). Don't just take passive notes—open your browser DevTools Console (F12 -> Console tab) or VS Code and type every code snippet out manually.
• 20 mins - Predict & Break: Change parameters or conditions in the snippet. Try to guess what will output before pressing Enter. For example:

const scores = [85, 92, 78, 95];

// Instead of just reading about loops, build a quick accumulator:
let total = 0;
for (let i = 0; i < scores.length; i++) {
    total += scores[i];
}
console.log("Average score:", total / scores.length);

• 50 mins - Small Unassisted Challenge: Close the tutorial/doc tab and build a tiny mini-project without looking at the solution first. Examples:
  • Print only even numbers from an array.
  • Count how many items in an array are greater than 50.
  • Reverse a word using a loop.

2. Ditch Heavy Note-Taking for "Active Recall"

Writing long notes from MDN slows you down. Instead, keep a "Cheat Sheet JS" file where you only write 1-line code examples of patterns you actually built and debugged yourself.

3. Debugging with console.log()

Whenever a loop or array operation doesn't make sense, print state changes inside the loop iteration:

const items = ['apple', 'banana', 'cherry'];
for (let i = 0; i < items.length; i++) {
    console.log(`Index: ${i}, Item: ${items[i]}`);
}

Seeing the output step-by-step makes abstract array indices feel tangible!

How are you currently running your JavaScript code while working through TOP—are you using Node.js in the terminal, or browser console/HTML files in VS Code?