Now that I am teaching my kids how to code with the help of online courses I can see where instructors take the wrong turn. By now, I mastered the material myself, and can put myself in the position of someone who is trying to understand it (I was there myself a year ago).
One mistake is a side track trap. You introduce a completely new concept, but before explaining roughly what it is about, you introduce a few exceptions or unusual use cases where you could also apply this new concept, that the presenter has not fully introduced yet).
From a logic flow perspective, this could look great: we cover all the use cases together. From a teaching perspective, this is confusing. A reference video (‘How did that work again exactly?”), is different from a 101 introduction video.
I am not sure the instructor does this intentionally. Maybe videos get edited later and she needed to find a place to insert this specific concept, “plop”, this seems like the right spot.
Notice the difference between detail and side track. If you need to go into the details to explain something, a newbie can probably follow along as long as you stick to the one specific use case of pieces of information that reinforce each other. Leaving things at a high level (i.e., no details) but lots of different tangents can still be very confusing for the newbie.
This relates to the blog post earlier this week, where I discussed answering questions with the risk of tripping up your story line.
