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 Object-Oriented JavaScript (2015) Practice Project Quiz Prototype

Karl Wills
Karl Wills
4,110 Points

I understand the theory of what we have learned, but struggling to put it all into practice...

I've enjoyed this course and have learned a great deal about Object Orientated JavaScript. However, I'm finding it increasingly difficult to complete these code challenges using what I have learned along the way.

Going through each of the videos, I find myself having a good understanding of what each command is doing, and why we use it.

The issue I'm having is when we are asked to build something like the quiz application, I begin to struggle when planning on how I should approach it, and what the best way is to execute what needs doing.

Does anyone else have this same problem? I'm at a point now of wondering whether or not I should go back through the videos (again) and try to further understand they way Andrew approaches tasks like this, or carry on and hope I start to understand everything a little more?

I have seen previous videos of Andrew approaching the ToDo Application, and tried to use the same principles that he used to complete this task for the quiz application. It worked for a short while, then I got stuck and decided to watch how he completed the task and manipulated what I had to match his solution.

I feel like I am cheating myself sometimes by just watching Andrew in his videos and copying him. Can anyone recommend a better way of doing things? or can anyone recommend any resources on how to think more like a programmer, and how to solve these types of solutions?

Thanks :)

6 Answers

Maxwell DeMers
Maxwell DeMers
6,853 Points

This may seem like a cop out answer, but it is still applicable. You will always struggle, and the best way to get through problems like these are to just push/test/ask/ponder/repeat. What Ronan said above is perfect as well. Think modularly. I break down everything when I approach a project, before I start with the actual code. I think through what I will need, where it will be stored, how to scope it, and so on.

Also, don't feel any shame in looking at how the instructors solve the problem. You will always find something that slows you down, and after you give it your best effort, you may need someone to show you how they did it. Remember, there are dozens of ways to solve a problem, and what the instructors show you is only one.

For a resource, once you complete the the track/course you are one, take a look at freecodecamp.com. It offers a lot of good challenges(algorithms and projects) to give you a lot of practice.

Hope this helps. Happy coding!

Ronan Cleary
Ronan Cleary
5,139 Points

I'm only just starting out myself but Personally I've found writing down on a note pad step by step what I'm trying to do very helpful. In essence I break down a big problem into a series of smaller more manageable problems. I.e the first step could be asking the user for an answer using a prompt box that we store in a variable. The more you can break it down the better. Look into code flow charts as well they are very useful for visualising how a program is going to run.

Christopher Parke
Christopher Parke
21,978 Points

Some challenges are easier than others. This was the first one where I gave up and looked at the answer. It was no where near what I was doing / thinking. Sometimes the intellectual leap is just a bit far and you need to build another step stool of knowledge to make the jump.

Christopher Stuart
.a{fill-rule:evenodd;}techdegree seal-36
Christopher Stuart
Full Stack JavaScript Techdegree Graduate 27,771 Points

Same here-- glad I'm not the only one. Probably toughest thing I've encountered at Treehouse---felt roughly the same way about OOP in Python--so I think it is just a challenging topic overall.

Brian Patterson
Brian Patterson
19,588 Points

Just reading the above post has given me some heart. I got some of it right and in other parts, I was way off the mark. The thing that gets me is what are his thought patterns. How did he get that answer! I think the best way to approach these challenges is to think "I am going in the deep end and now I really am going to learn to swim!". It's going to be depressing and you will be upset. But in that moment, your on your own, you learn something (no matter how small) it will be worth it. It has taken me a long time to appreciate this.

Tushar Singh
Tushar Singh
Courses Plus Student 8,692 Points

Me too, sometimes I face the same thing you mentioned, because yes things sometimes gets a little tricky. Basically what I do is just keep on trying and trying and finally you/I will come up with a solution, that's a promise.What I've learnt over this learning period is that frustration will find you, I mean that's inevitable,right? But I guess I have learnt how to cope up with it and keep trying again and again. Why don't you build something quite similar to the projects in that particular course, at least it helps me a lot. In the end, it's all about practice. Good Luck!

Karl Wills you couldn't have said it better. Everything you said is true for me too. Keep on Coding!!!

Best of Luck!!!