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
Keturah Hurley
1,481 Pointsnewbie confusion
How do I know where a good stopping point is? I'm not sure if I am ahead in the game or way behind. I feel like I've missed important information on where I stand in my course.
2 Answers
Jay Padzensky
4,731 PointsHey Keturah,
In my opinion, stopping points will vary person to person. For me personally when studying with Treehouse, I tend to set manageable chunks of time aside (30-60 minutes) and try to find an organic ending point within it (for example, completing a stage [earning a badge], or ending after a quiz or Code Challenge). I think the important thing is to remain motivated by not overdoing it and reviewing content as necessary so you don't get further down the rabbit hole getting more and more confused. Don't worry about being behind or ahead of the game, so to speak. If you're looking to become a programmer, competition while learning is less important than learning the fundamentals and growing at a pace that makes sense to you because ultimately, you're going to need to be able to recall all of this information to use it (or know how to find answers).
christopher abramson
22,741 PointsGo back, review, and follow along. I've learned more and more with every review. You can also dig deeper into the API docs on each subject if you want maximum knowledge!