Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript JavaScript Loops, Arrays and Objects Tracking Multiple Items with Arrays Build a Quiz Challenge, Part 2 Solution

maya sophie
maya sophie
5,754 Points

It is a solution for learning all those things in this challenge?

I was looking how Dave did the challenge and I must say I watched it straight away without even trying alone. Why? seeing the answer I realized that I did the correct thing because I would of never pass this challenge by myself. The only solution to be able to learn to write codes is in my opinion this :

  • watch the solutions ,then open workspace again and try to reproduce all the code....and try to understand why is everything there...and when I just can't understand, I try to memorize the way it was done hoping in the future I will understand. Please leave some comments if you feel the same. And for this quiz, with all those 'convert' js to html ....it may look simple for some one who codes for long time but when just throw there, IT'S NOT !. My impression in this challenge : bad!...I feel like this challenge it was explained in a rush and saying " like you saw in other courses before" doesn't help! P.S. html +=......when did we learned we can display next message in html in this way?....in a for loop I understand it jumps to next one, but here?......I realize that I pay monthly to go myself on MDN or W3C and start studying from there...

P.P.S. .....After reproducing all the code in the solution, it ' s not working !!!!!!...I'm done with this!!!!!!!!!!!!!!!!!!!!!!!!

2 Answers

Hey Maya, I actually remember this lesson too, and agree that there was too much going on there to wrap my brain around at the time. Dave's solution does work, but there are so many places where some tiny bug might have found a way in and caused your solution not to work, and it's too complicated a project to really teach the concepts as well as it could. My advice? Just move past it. There are lots of JavaScript courses in Treehouse that are better-paced and will help you learn things. And you're right, I would totally recommend MDN and W3Schools -- and Codecademy and YouTube vids and Udemy and whatever else -- to help you learn. JavaScript itself is pretty gnarly, so it requires a lot of time and seeing things different ways before things really sink in beyond the most basic parts. Treehouse is a good foundation to branch out and sample those other things from.

One thing I will add, in case it helps in a larger sense: I've been doing this stuff for almost a decade and I still get stuck. All. The. Time. With web development and programming, you will very frequently need to go look stuff up a few places because your code is broken and you don't know why, or you need to do something and you don't know how. It can be super frustrating. Literally everyone I know who codes for a living has to regularly watch tutorials, read articles, search Stack Overflow and more to fulfill their job duties. Thing is, they (and I) like that part of it: being able to cobble together knowledge to get yourself unstuck can be a thrill. I hope you can start seeing it that way too, because believe me it won't change that much as you get deeper into coding.

Emanuel Rouse
Emanuel Rouse
1,985 Points

Trust me it seems difficult now I'm going through similar frustration. However don't give up. If you are doing this for the right why then you'll get through it in my opinion. Take it slow and one thing I've learned is not to trust your eyes. I always make sure to scan each and every line for one missed detail whenever I run into a bug. You'll be surprised what information your brain can omit and 9 times out of 10 that's what's causing your code not to run. Hope this helps.