Thank you so much for leaving such thoughtful feedback, Jason :) Actually, this was something I thought about a lot while preparing this course, so let me comfortably share the points I considered. There are 3 reasons why I re-explain certain parts: 1. Re-explaining important concepts. Important concepts must be understood, so repeated explanations are necessary. 2. Explaining previously learned concepts from a slightly different perspective. This way, you can review previously learned concepts through a slightly different context and understand them more clearly. 3. Maintaining the flow. Even if you don't immediately recall what you learned earlier, briefly mentioning it here allows you to continue the overall flow without interruption. There's a difficulty here though. The range of people taking the course is very wide. For those in the top 10%, since they already understand all the existing content well, points 1, 2, and 3 actually feel redundant to them. For the rest, points 1, 2, and 3 help reinforce what they learned earlier and allow them to understand it better. Since I'm also a developer, I really want to eliminate redundancy as much as possible and proceed like method calls 😊😊 However, in education that considers beginners, reviewing previously learned content from various perspectives and slightly different angles is helpful. When preparing lectures, the thoughts that keep running through my head are "If I just explain this part, beginners probably won't understand it, right? Let me bring more from the previous content and summarize it for explanation" versus "This part seems to have too much repetition. Let me boldly omit it" - the scale of balance in my head is always fighting repeatedly. So I'll think about how to carry this kind of repetition while being considerate of beginners, but deliver it more concisely and effectively :) Oh, and I draw all the images directly using Keynote :) Thank you.