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 trialAndrei Li
34,475 PointsEducation strategy to implement in Treehouse. My view after being two weeks on the site.
Hi!
I am two weeks with Treehouse now. So some courses are really awesome but some are really tough. I want to continue learning, so I am not leaving.
If you are on track you've to get used to different education stratagies that teacher present. It makes us feel tired.
So, I decied to post for Treehouse to improve it's stategy.
- Every course should be introducted to create a map that you fill in later with knowledge.
- The introductory should be no more than one video. 15 min maximum.
- Should not use complex definition. Keep things simple. At the same time all definition must be exact as they apper in an official documentation.
- Explaining particular method teacher should mention main parameters of the function ana make an example of the most widely used feature.
- In one video there should be no more than 4 functions with description.
- Every function should be tested in multimple choice questions.
- Referencing with video should be simple. When you use function you remember how to use it.
- Each video should be a good reference. Teacher shouldn't bouncing from one topic to another or present function than switch one window to another. Each function with explanation should appear in the video and should be on the screen at least 20 seconds.
- Questions in multiple choices should be smart. But they should progress in eact section. Sometimes choices are really naive.
- Projects should start from fundamentals. Not starting from a beutiful smart idea that teacher enjoy and should cover fundamentals and should progress with steps. Teacher should write a function, then context of the function, then and only then smart things that leads to extra points. Not everybody wants smart structures. So it's not an obligation to take it.
- Algorhytm for checking projects should be changed. First, syntax, second, meaning of the code. Syntax is checked by the computer and if there is an error there should be Treehouse explanation why and what. Meaning, teacher have to use structured approach before writing a code to catch the meaning of the task. Check if the construction exist, check if it's correct, check that's working.
- In projects should be hints. Googling is a good practice but hints should be in projects.
- Course should be light in understanding and not to be overloaded.
- Teacher's note. Not everybody wants to read. Video should be enoug to answer questions.
- If teacher content exist. It should be divided in general theory , like a link to MDN, reference, advanced material. All content should be specific to the video.
In summary, Treehouse education should be fun and enjoyable.
Good luck!
Steven Parker
231,271 PointsSteven Parker
231,271 PointsIt took a little over a year, but according to this other post, it looks like your suggestion #12 got implemented!