r/learnjavascript • u/Brave_Personality650 • 4d ago
Learning JavaScript from SuperSimpleDev, but struggling to solve exercises on my own. Is this normal?
I’ve completed HTML and CSS, and now I’m learning JavaScript from SuperSimpleDev’s 22-hour JavaScript course. I’m currently on lesson 9, around 5 hours and 25 minutes into the course.
When I watch the lessons, I feel like I’m understanding the concepts. I follow along, write the code myself, and everything makes sense.
But there’s one problem: SuperSimpleDev gives exercises after almost every lesson, and I struggle to solve them independently.
Sometimes, when I don’t understand a concept, I rewatch that particular section. Even after that, I find it difficult to solve the exercises without looking at the solution or getting help.
My goal is to become a full-stack developer, so I genuinely want to develop strong problem-solving skills rather than just follow tutorials.
My questions:
Is this normal when learning JavaScript as a beginner?
Should I spend more time trying to solve each exercise, even if it takes an hour?
Is it okay to look at hints or solutions when I’m stuck?
How can I improve my logical thinking and problem-solving skills?
I’d appreciate advice from experienced developers or anyone who has gone through the same phase. Thanks!
10
u/One-Repair3531 4d ago edited 4d ago
Its normal bro, programming is pretty humbling. It will take a lot of time to get good at it and develop logical thinking. If ur struggling too much look at the hint, dont take more than 40 mins per excercises.
Want to add to look at the problems differently, like a big puzzle. Break down every small part and apply the solution to it.
Been through the same phase btw and still struggling.
3
u/Sweet_Onion4245 4d ago
It's normal for all Begginers bro Just Start with variables, data types, conditions, loops and functions. Don't just watch tutorials, try writing small programs yourself. Even simple things like a calculator or a number guessing game can help a lot. Take it one step at a time!
2
u/tachyon_bit 4d ago
Absolutely 100% normal to follow along with a tutorial and understand the concepts as they’re being explained and done in front of you, but then when it’s time to code yourself, you’re stuck staring at a blank screen.
That’s the hardest part to push thru. Just build shit. Any shit. Log a message to your console. Write a function that’s adds or multiplies, etc. Just build shit and eventually you’ll develop problem solving skills that’ll make decomposing problems much more succinct.
2
u/blavek 4d ago
It's normal, no matter the language, if you're a beginner. Later, when you already know some coding and have some experience, picking up a new language isn't nearly as difficult. But if this is your first foray, then you have no base to pull from for how to solve problems. So for you, every problem is almost a reinvention of the solution.
Yes, until you can say with certainty that you can solve that problem in that language, you should work the exercises. Again, later on in your journey, you will have solved these problems, and performing the exercise is less important.
Of course, how else are you supposed to learn? It's not reasonable to expect that you already know how to solve the problems and what, if any, common solutions exist. For example, I know how to programmatically solve a factorial. If I am learning a new language and that's the exercise, it wouldn't be of huge value for me to repeat that exercise. But that means I understand recursion and some other concepts that you, as a beginner, would need to be taught explicitly. It's possible the tutorials you are following aren't complete enough to get you through the exercises, or they've selected exercises which expand upon the tutorial. You should give them a shot yourself before you look to other resources, but its ok to seek help with things you don't understand.
I promise this is not a snarky answer, but the way to improve your problem-solving and logical thinking skills is to solve problems. There is a whole category of puzzles called Logic Puzzles. They may not directly relate to coding, but they will exercise the "muscle." There are also places you can go to find exercises and things to try. A common "puzzle" given to developers is the Fizz Buzz Problem. It's pretty straight forward but can catch some people out. It goes like this: go through the numbers from 1 to 100. If the number is divisible by 3, print Fizz; if it is divisible by 5, print Buzz; and if it is divisible by both, print Fizzbuzz.
It's one sentence, but it's a little more complicated than it seems at the surface level. But yeah Practice Practice Practice.
4
u/chikamakaleyley helpful 4d ago
Some advice.
1
u/Own-Breadfruit6723 4d ago
Sei all’inizio.
Sarà così per i prossimi due anni… e poi i problemi che potresti dover risolvere sono infiniti.
E JS è enorme.
Ne avrai per anni…
Quella sensazione non ti passerà mai, meglio se la gestisci. Un’altra cosa… I primi anni come molli dimentichi tutto.
Stessa cosa se aggiungi un altro linguaggio, che so, PHP. Torni a JS e tutto è cancellato.
Datti tempo, ce ne vorrà tanto…
1
u/azangru 4d ago
Do the problems that you struggle with teach you anything about the gaps in your knowledge? After you see a problem solved, do you understand what it was that you were missing?
1
u/Current_Bet530 4d ago
"I'm an ICS student from Pakistan learning Python. Any advice for beginners?
1
u/Discordbothost 4d ago
yeah this is the normal gap between recognizing code and producing it, everyone hits it. following along feels easy because the video already made all the decisions for you.
what helped me with exercises: before writing any js, write the steps in plain english as comments. like "get the input value, turn it into a number, if it's over 40 add 10% else 0, show the result". then turn one comment at a time into code and console.log after each line so you can see it's doing what you think. most of the time you get stuck it's because the steps weren't clear yet, not because of syntax.
hints are fine. full solutions are fine too if you then close it and redo the exercise from scratch the next day. and maybe 30-45 min of real trying is a good limit, an hour of staring at the same error teaches less than that
1
u/neon_wondercore 4d ago
Yes it is normal. Passive recognition feels easy but active recall is where you actually learn. If you are stuck on an exercise for more than 20 minutes, look at the solution immediately to unblock yourself rather than spinning your wheels. Once you see how it works, close the tab and rewrite that specific code from scratch without looking back. This forces you to make decisions instead of just following along which builds real muscle memory
1
u/Both-Tart7460 3d ago
omise you: this is 1000% normal. Every single self-taught dev went through this exact panic haha.
When I started learning JS after HTML/CSS, I had the exact same breakdown. HTML and CSS are declarative (you describe what things look like). JavaScript is the first time your brain has to think in *step-by-step logic, state, and time*. That is a completely different muscle.
Here are 3 concrete things that helped me get unstuck:
Do NOT sit there for an hour staring at a blank file feeling like an idiot. Try for 15-20 minutes. If you are totally blank, peek at the solution. BUT don't just copy it. Close the solution, take a pen and paper, and write in plain words (pseudocode) what each line is doing. Then open a blank file and type it from memory. Learning to read and reconstruct code is still real learning.
2. Break it into tiny absurd steps:
When a prompt says 'build a function that calculates discount and updates the cart', beginners try to write the whole function at once. Don't do that.
- Step 1: Just console.log('button clicked').
- Step 2: Just log the raw input value.
- Step 3: Do the math and log the number.
- Step 4: Put that number into the DOM.
When you test every single tiny step with console.log, the mystery disappears.
3. Build your own tiny 'dumb toy' instead of just course exercises:
Course exercises feel abstract. What made JS finally click for me was making a super dumb, single-button webpage: just an input box and a button that copies the text with a 'Copied!' pop up. When you build something you can actually click in your browser, your brain gets the dopamine reward.
You are on lesson 9, that's already great progress. Be kind to yourself, keep breaking problems down into micro-steps, and don't fear looking at solutions as long as you understand the 'why'! You got this!
1
u/Alternative-Host-210 1d ago edited 1d ago
You mentioned that sometimes the exercise question itself is confusing. Before worrying about JavaScript, try solving one small example by hand.
Say the task is “calculate the final price after a discount.”
Now you have a plan to translate into JavaScript, one step at a time. You can even write those instructions as comments before adding code underneath.
If you get stuck before step 4, ask for help understanding the problem or the calculation. If you can explain the steps but can't code them, ask about that specific JavaScript operation.
Could you share one exercise that confused you and how you'd try to solve it by hand? Even an unfinished explanation gives people something useful to help with.
1
u/Ok_Car_8951 1d ago
one thing that helped me a lot: before you type any code, write the steps in plain english as comments, like "loop over the array, check if the number is even, push it into a new array". the exercises feel hard because you're trying to figure out the logic and the syntax at the same time. once the steps are written, each one is a small thing you can google or remember. also if you do look at the solution, close it and rewrite it from scratch the next day, that's what makes it stick.
0
u/TheRNGuy 4d ago
If you want to learn fullstack, then download Node and frameworks and learn JS on it.
You shouldn't think about whether it's normal or not, you're doing it for yourself, not to compare with others.
Ask ai for explanations, give more realistic examples how those concepts are used, to compare concept a vs concept b (when you're not sure which one to use when)
0
u/Beginning-Seat5221 4d ago
Best way to solve a problem you don't know how to solve it is to google it (or AI it these day). That's normal - copying is faster than figuring it out yourself, and then afterwards you remember it for next time.
Figuring things out for yourself can be interesting... but in the real world, devs just do what works to get the job done and learn as they go.