Welcome to the Treehouse Community
The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.
Manish Giri16,266 Points
Need more diagrammatic representation/explanation of the desired functionality instead of diving into code right away
I'm not sure how to accurately describe this, but after a certain point, it gets really hard to figure out what exactly it is that we are building. The last few videos about the "slug" and vote-count (starting with about the 2nd-3rd video in the "Bells and Whistles" section) features, and the ability to add votes, have all been a big blur. All you did was throw out a one-liner stating "we'll be building XYZ feature", and immediately started writing the code for it.
It's obvious that you're just writing code that's already available to you beforehand, but that's not really a great way to create a tutorial, especially for someone who's just starting out learning these technologies. Instead, a better approach would have been to first start out with an architecture diagram of what it is that we're attempting to build, and how it ties into the rest of the current application. As an example, you just started writing the code for the ideas (and votecount) template, and only after looking at the HTML structure, could one figure out what exactly you were trying to build. It should ideally be the other way around - you start out with a diagram or the layout of what you're trying to build, and then you write the code for it.
At this point, it's become really hard to keep track of what it is that we're attempting to build. You're just introducing new features in every video, and immediately diving into the code for it.
Yeah I am also having trouble following the actual intent here. A UML of what we are aiming for would be SO helpful. I don't even understand how the different parts of this application work, i just know that I typed in the code and suddenly idea.hbs is able to pull info from my CourseIdea.java class? I get that we put something named "idea" in our model, but how does that access data from a class?
A real diagram for our MVC would be so unbelievably helpful here..
Original post was over a year ago I completely agree. I have to watch the videos twice.