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!
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
Christopher Gregory4,183 Points
Sorry if the question sounds a bit stupid . . . :P
I understand what you mean. What I started doing towards the beginning is listening to the plan until I felt it clicked, and then I'd go work on it until I got stuck. Then I'd watch more, fix my code, pause again and try to make more headway. Clicking around the documentation also helped.
Sometimes I would need to watch well into part of a problem before feeling like I could make progress on my own, but I definitely think it's helping to try to do as much as I can in each section. You always have the videos and finished code to fall back on.
Also, after finishing a project, I'll sometimes try to build something similar to reinforce the concepts.
That's not to say my method will work for you. But you're not alone! Getting started on a project is the hardest part I think.
Leonardo Hernandez13,798 Points
It is normal in my opinion. Try your best at and compare your attempts to the solutions they give.
What really helps me with larger problems, like these challenges, are writing step by step instructions on paper. Then translating them to code.