This is the most frustrating practice session in this course.

Yeah I agree. I feel like it's just a bit too complex and only briefly explains what everything does.

I am loving this practice. It is great to see a whole project come together, even if I don't fully understand all the individual parts yet. I do think it would be better to have more opportunities to check your code and test what you have done along the way. It is too easy to make a small typo and then when you test it several steps down the road, it is hard to go back and find where you made a mistake.

I have not found any concepts here that were not covered in the OOJS course. The OOJS stuff takes lots of practice. I keep forgetting to prepend 'this' to all my function calls, lol.

I'm finding this very complicated too compared to what I have already encountered on the Full Stack JS track, but I would imagine we aren't supposed to be able to make this on our own - it's just a thorough explanation of a more complex JS application, rather than the trivial code we've been playing with so far.

I have already make the react course and understand it, but this is another level step ahead as well and can´t really click it. Too complex

I fully agree with Jeremy Antoine's feedback. I like it so see how everything comes together and how it let me think a bit like a developer. It's fun!!

Yes. I'm very frustrated. Would've preferred a smaller project to start with to get a handle on how the different classes, getters etc connect with each other. Maybe just a tic tac toe game or hangman. We started off from scratch, but somewhere I feel that she stopped letting us think and just started telling us what to do. She admits there were several iterations before she got to this solution. I would have liked to see how to psedo code this from start to finish before starting to code. Setting up the classes and constructors was fine but later I felt that we were juggling so many pieces, partial builds that I lost track of the main road. No way, would I be able to put this together on my own. It's neat to see what is possible, but I'm going to have to run through this many, many times.

While I get the thinking like a developer bit, I must agree that it's more frustrating than not. There is a lot of stuff that's in here that isn't very well explained. I'm finding that the ideas being introduced here aren't sticking as well as previous ones. I'm also finding the documentation not up to par, as there are parts that feel like typos or things that are left out altogether. For example, the Jquery challenge...I am doing the Fullstack Techdegree, and this hasn't been mentioned at all to this point. It's mentioned in this challenge, but there's no link to anything, which was annoying. At $200 a month, I'd like a little more resources or explanations regarding new concepts. I know that I'll need to Google things (and I do), but I'm paying for this to help teach me...At this point, I know exactly the same about Jquery as I did at the start of this challenge, which shouldn't be the case. Sorry for the rant :/ This game has a lot of moving bits that call on and connect to one another. I'm pretty sure I'll have to revisit it later on.

Following the Full Stack JavaScript track, this project really throws you in at the deep end. Prior to this, there's a tiny section on OOJS. I've followed the whole course perfectly up until this project. I'm finding it hard to follow along, and there seems to be a lot of 'this is the code to write, copy mine', rather than 'we're going to write this code because....'

Glad to know i'm not the only one feeling a little out of my depth here.

I am personally enjoying this course but man is it frustrating. This seems like something for intermediate OOJS programmers, but despite that it is actually quite fun. It puts you in the mind set of a programmer that has to take on a challenge.

I did the animation challenge and got it dropping with a fixed level of depth (while using a token to express this) and moving on to the next token. The minor frustration is that I think some of the videos document making changes where the code didn't strictly work. If she doesn't say the precise outcome of the change, you might run it and see errors and be uncertain if you've done something wrong or whether that's exactly what's meant to happen pending the next modification.

Agree. Lost. Will need to review most of this material. Maybe coding isn't for me. Ugh.

I have also felt confused and frustrated with this project but at the same time, I think it's important. Having to look at something confusing and research and go over it again and again until you understand it, is something I believe we will have to do in the real world on a regular basis. This is the kind of field that will regularly leave you confused and frustrated. Learning how to overcome that and push through is necessary. I think the only real issue I have with this part of the course is that (at least to me) there was little to no way to test what you wrote yourself until we got father into it.