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: Challenge Adding the Game Logic checkForWin() Method Challenge Solution

Guilt for not attempting this part

This course has taught me a lot, but I'm getting a little burnt out and since the drop() task, I've been feeling a bit of imposter syndrome.

I didn't know where to start when having to think of how to check for the win

Blake Larson
Blake Larson
13,014 Points

We have all been there. Eventually it will click when you get more practice.

I'm feeling the same during this practice. I've decided to revisit it later on :)

Trevor Maltbie
seal-mask
.a{fill-rule:evenodd;}techdegree seal-36
Trevor Maltbie
Full Stack JavaScript Techdegree Graduate 17,021 Points

I feel the same way. I don't know if it was burnout or just feeling overwhelmed with how to even think about formatting checking for a win. I decided to just look at the answer and to review it. I would like to at least understand the process and why it works even if I didn't come up with an answer on my own.

I think your feeling is not unique. We are just at the beginning of our coding journey (a journey that may never really end anyway) and I think perseverance will be instrumental in our success.

Happy .
Happy .
11,414 Points

bit old school i think these days, but... familiar with using pseudo code?

  • break the problem down into basic steps, which work towards the solution. you can then iterate over the steps and refine them to solve the issue.

problem: How to make toast:

  1. get bread
  2. insert bread into toaster
  3. turn toaster on
  4. wait til it pops
  5. eat
Simon Coates
Simon Coates
8,223 Points

I'll admit I didn't have a clue until she said that you check at the point of dropping. I demos bits of pieces, made mistakes and had to try and then used pen and paper and very incremental design. I came up with a solution in the end. I think writing things method by method kinda focuses you on the tiniest section. I felt like I was losing focus on the overarching design and wasn't sure what high level concept we were supposed to be absorbing.

3 Answers

I think perspective has a lot to do with it. Don't forget that you're learning a new language here...and this language is full of math, logic, puzzles, grammar, and nuances that you have to get a grasp on. Make sure you're keeping a growth mindset and that you are reassuring yourself that learning doesn't happen immediately. Even when you get a job as a developer, you're going to have to keep learning. A career as a programmer is a non-stop journey of learning...this is just one step on the path.

Also, I like to go back to previous courses and look at the questions under each video and answer them if I can. It helps me realize how far I've come in just this short timeframe. It's also a great reminder that we all have to start somewhere.

Anyway, chin-up...toss that guilt out the widow and keep on coding!

Leah Miller
Leah Miller
16,291 Points

Thank you for asking this! I couldn't wrap my head around it either. I knew what i needed to do but not how to do it with code. Seeing the answer was a 'duh' moment so i was questioning if I know the material as well as i should at this point.

Joe Elliot
Joe Elliot
5,330 Points

Hahaha I was feeling the same! Didn't even attempt it because I felt I didn't know where to begin. Saw some other people's answers and felt incredibly out my depth.

I think our skills just aren't there yet. And that's okay. We're still learning from this.

I'll just watch this last section and try the whole module again at some point.