I want your feedback on Android Code Challenges

Ben sorry, I know this isn't in regards to this post. I REALLY NEED HELP on the crystal ball project and no one is replying to my threads in the forums i've tagged you in both

1.Do you think the Android Code Challenges are valuable? Normally they cover what we´ve learned on the last vídeo, so for me is a way of exercising and yes, they are great for learning.

2.What do you like about them? The chances of practicing the codes.

3.What do you dislike about them? Sometimes i really hate them, but then i take a deep breath, rewatch the last vídeo and there it is. 90% of the time i´ve finished the code challenge just by rewatching the vídeo, 10% using the forum.

4.Should there be more or less of them? I think it´s good how it is, but you could add my suggestion of the next question.

5.What other suggestions or feedback would you like to share about them? It would be good if we get some quizzes about what something does, like "doInBackground do" blablabla. the "OnClickListener is to" blablabla. "If your button doesn´t work, what should you check". Something like these.

good luck on the new Python course, ill be there when its ready!

1) Yes, the majority of the code challenges are very valuable and great for actually learning instead of just following along.

2)The fact that you are forced to do it yourself instead of follow the teacher, allows for actual brain power to be used.

3)They are very frustrating sometimes I would say a good 25% of the time I have to get some tips from the forum. My personal recommendation Add a Hint like codeacademy.com has on there lessons, It doesn't spoil the answer but it refreshes my mind and keeps me from having to take an extra trip to the forum.

4)More with less in them, I feel like if you had more you would learn the lesson better and with less it wouldn't feel as tedious.

5)Maybe some new rewards for getting like 3 100's in a row or something. Just an extra reward to surprise me every now again.

Once again thanks for the help on my lesson

Hi Ben, First of all thanks for the great content. Now here is my feedback...

1. I feel the Code Challenges are great for reinforcing what was just learned. I do believe a final Challenge should be given at the end of each track section.

2. First, what I stated on question one and that they give me more hands on with the code... practice makes perfect. =-)

3. I have a hard time keeping track of all this new terminology, otherwise I have no other grips.

4. Back to question two I believe there should be a, for lack of a better term, a final Challenge. On a little side not a small test on terminology or a list of what is covered on this the track would be helpful.

5. Other than they are a bit buggy at times, there is nothing else I can think of that can help.

As we say in my family, work smarter not harder. Thanks again

=-)

Code Challenges are great and I feel like there should be more of them. I would also agree that if there isn't a Hint given, that is fine, but would like the Forums to be better filtered so that we can quickly go and find help.

Ben,

First of all great content, maybe some more on java example: hashtables, but none the less you are awesome

1. The code challenges are of great value second only to performing all the code yourself and purposefully break it log the error understand what is happening when a certain error occurs. But they are quite valuable I really agree with David and Dan that there could/should be more and even final ones after each section.

2. I like the fact that it allows for hands on validation. I learn something for example but how does one feel validated. Oh I learn something then I take a test and it says I learn something, validation. Sometimes you feel like you are walking on a tight rope by yourself and your going to fall and only mike can catch you. (The last comment is more about the journey of learning than your class)

3. I don't really dislike anything about them. Except sometimes as David pointed out they will bug out and it states that the code is wrong but I can pop it into my editor and it compiles and executes fine.

4. Again see answer in question 1, more couldn't hurt.

5. It would be nice to mix them with a, well make us the compiler. Not to steal the gusto from the head first series but I think it works for a lot of people give us broken code and the error make us think about why the compiler is complaining and what the error is referencing. I would say that being a great programmer goes hand in hand with being a great debugger. The best guys I have met in the field can explain exactly what the interpreter or compiler is doing at runtime and how that will affect an application.