r/learnjavascript • u/Brave_Personality650 • 3d 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!
3
u/Sweet_Onion4245 3d 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!
1
u/Brave_Personality650 3d ago
Yeah bro you are Right. I really need to make smth whole programming but what should i do if dont even understand his Exercise Question? And about calvulatot i had build it two days ago which is in his Exercise just a simple calculator like buttons and onlick return if else normal
Thanks Man!
4
u/chikamakaleyley helpful 3d ago
It's normal when learning how to program, CS concepts, fundamentals, period.
You should spend as much time as you want on any question as long as the gears are moving. I don't know the relative time to someone who is a beginner, BUT, if I find myself spending, you know 30 min STUCK in one small area, then I've already spent too much time on that thing. I'm stuck, because something - whether I misunderstand it, i tried to get too creative, or I have a typo - something incorrect got me there. That's when you take a moment, stop coding, and kinda review what you did.
With AI availability nowadays, getting un-stuck is fast, you just want to avoid asking for the answer. It's okay to look at hints, the problem I've always had with hints is all the surrounding noise (text) that possibly contains an answer. That being said - sometimes, I just need to see the answer up front, because something just might click. Sometimes when I see the answer, it's much easier for me to unpack it and figure out the steps to get there, which is the real important part.
Spend more time thinking about the problem before you type a line of code. If you can't understand something because its the next level, or its too complex, break it into the smaller pieces that you do understand.
Some advice.
JS is a programming language like any other. It has building blocks - variables, conditionals, loops, objects, etc. You'll find these things in any programming language. You can write something that runs in your terminal with just JS. When you introduce HTML + CSS, you're using JS in the specific context of a web browser, and it will feel foreign. You can build a fully functional page with just HTML & CSS. They have their own roles. With JS, you're just augmenting that, and you're doing that by using all those building blocks you learned.
w/ regards to how much time I spend on a problem - sometimes i just need to step away from the computer and let the problem marinate in my head. I can go fold laundry and think about ways to solve the problem. Or run an errand and think about it. It's generally worked out for me, because when I get back to my keyboard I at least have an idea to try out, a plan, whether or not its correct.
1
u/Own-Breadfruit6723 3d 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…
0
u/Brave_Personality650 3d ago
I didn’t understand your language at first, so I put it into ChatGPT and understood what you meant. 😂 And yeah, you’re right!
I’ve been learning JavaScript for barely 15 days, and I’m already stressing about how huge it is, solving problems, and mastering everything. I think I’m expecting too much from myself too early.
Your comment actually reminded me that programming takes years to get good at, and I need to be patient with myself. Thanks for the advice, bro. Really appreciate it! ❤️1
u/Own-Breadfruit6723 3d ago
Haha, I didn’t realize Reddit was showing my comment in Italian! 😂
Anyway, don’t put too much pressure on yourself. I’ve been programming for over six years, and I still regularly come across things I don’t know or have forgotten.
The important thing isn’t remembering everything, but learning how to approach problems and find solutions. That comes with experience.
Keep going, and enjoy the process! 🙌🏻1
u/Brave_Personality650 3d ago
Haha!😂 yeah will try to solve more rather than putting pressure on me and will take care
Thanks Bro really appreciate it!
Btw can we connect in DM?1
1
u/tachyon_bit 3d 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.
1
u/Brave_Personality650 3d ago
Yeah bro, that’s exactly what happens with me. I can follow along with the tutorial and understand what’s going on, but when I have to write the code myself, I sometimes just stare at the screen. 😂
I guess I need to spend more time actually building things instead of focusing too much on completing the course. Thanks for the advice, really appreciate it!1
u/tachyon_bit 3d ago
100000%
You’ll only learn how to truly engineer and think abstractly thru trial and error. Literally building a little console program that asks for your name, age, job, etc etc, and then prints out that shit with some added text or whatever, is infinitely better than what’s referred to as “tutorial hell”. By all means, watch the tutorials. Follow along. But then make sure you’re building what you just learned on your own, and you’ll get there.
1
u/Brave_Personality650 3d ago
Frrr broo
Will try to follow this from tmrw for sure
But yk i can only give 4 hours daily and that too in Morning no after🙃
I think i need to do something with my Schedule too
Thanks Man!
Btw you do JOB? Or smth1
u/tachyon_bit 3d ago
Dude 4 hours is a fantastic amount of time to dedicate to programming, believe me.
And yea my job is software engineering.
1
u/Brave_Personality650 3d ago
Yeah ik but i am not that person like understand fast 🙃
And Wow your Job is my Dream tbh😭
Can we connect in DM?
1
u/blavek 3d ago
Is this normal when learning JavaScript as a beginner?
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.
Should I spend more time trying to solve each exercise, even if it takes an hour?
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.
Is it okay to look at hints or solutions when I’m stuck?
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.
How can I improve my logical thinking and problem-solving skills?
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.
1
1
u/azangru 3d ago
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.
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 3d ago
"I'm an ICS student from Pakistan learning Python. Any advice for beginners?
1
u/Discordbothost 3d 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 3d 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 2d 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:
The '20-minute frustration rule':
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 20h ago edited 20h 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.”
What information do you have? A price of 100 and a discount of 10%.
What answer do you need? The amount someone pays after the discount.
How would you calculate that yourself? Find 10% of 100, which is 10. Subtract that from 100, giving 90.
Write those steps as instructions: take the price and percentage, calculate the discount amount, subtract it from the price, return the result.
Try another example: a price of 200 with a 25% discount should give 150. Do the same steps still work?
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 18h 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 3d 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 3d 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.
1
u/Beginning-Seat5221 3d ago edited 3d ago
I'm confused why your reply was removed by a moderator, OP...
10
u/One-Repair3531 3d ago edited 3d 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.