This is going WAY too fast...You have to show STEP BY STEP what s going on in the code, from caller to callee!!!

Problems:

Notice that none of the moderators or the teamtreehouse Employees responded to this post. Its tone is more of a rant than a plea. Let me ask the question so that they should now have the obligation to respond.

[QUESTIONS] needing to be answered for the community:

Why is this C# Object instruction moving too fast for even programmers like me who have reviewed this (now 3 times)?

Why can't the instructor take a step back for each important part of the code and briefly explain what is going on?

Why are we discussing Exceptions and syntax sugar?

Why are we learning the wrong way first?

Regardless of the speed button to choose how fast or slow the instruction is played back, why does the instructor ( and most teamtreehouse instructors ) talk through the video so fast without taking appropriately timed pauses to allow the information to sink in?

Why doesn't the instructors give at least (at a minimum) two similar examples for each new subject introduced?

Solutions: Now some opinionated solutions when and if you decide to remaster the courses on teamtreehouse.

For instance, good practice with teaching is to ask the audience if they remember a step or terminology then proceed to go over it again as you code. This is called reminder repetition. This is very effective to get a target audience to learn without even forcing them. Assuming that generally, everyone at a certain point will have the understanding, confidence, and foresight to take on challenges or think ahead is just wrong. Especially for courses that are not advanced. At that level, it's best to make those assumptions early on.

Stick to the subject at hand and keep the code (and project) simple for beginners.

Let me say this a few times over to get exactly my point: Teach them the right way the first time! Teach them the right way the first time! Teach them the right way the first time! Teach them the right way the first time (or at least one standard to stick to) then show the wrong way it is done and why.

My opinion:

This is my third time coming back to these courses for just review while I look for employment and keep sharp. Each time I get more lost with the jumping around. I understand Objects, properties, methods etc but the way it is taught makes my gut wrench because I feel that it is rushed and the examples get too complicated. For example, do we need to jump into Exceptions right after learning C# Basics? Do we need to have half of an instruction block going over property syntax sugar and then the different ways not to write code before writing it the right way?

Final thoughts:

For anyone that clicked this title because they felt the same way, my advice to you is to go ahead and go through this course but please find another source to supplement this teaching style. Not all TeamTreehouse courses are taught this way but there is a good amount of them that rush through and just assume you know better.

As far as this course I can not recommend it to others as the first option to go to.

In the meantime i ve perfected myself using pluralsight, they ve got tons of better explanations and coverong way more subjects. They take you from no knowledge to developer junior developer status. To get further, you really need to go at it a different route, digital electronics course, serial communications course, then try building your own compiler, learning assembly and microprogramming