First of all, I am not in a complete state and I am listening to it all the time. Pros 1. There is no Python lecture that covers this much depth of topic - It is a fairly in-depth topic. It is probably because there is no demand for it because there are no people who go this deep, but it is a lecture that is hard to find, so it was very helpful to have it. 2. Direct typing during the coding process - It is difficult for beginners to know what each line of code, function, and typing mean, but it is really good to talk about the flow of consciousness while typing while coding. Cons 1. The topic is deep, but only the topic is briefly introduced and moved on - This is related to the pros, but... It feels like they are briefly explaining the in-depth content and saying, "There is also this." It would have been better if they had prepared the explanation in advance with a PPT or professional drawing, but it is a shame. Still, the examples are very helpful. Still, I think this is something I have to solve on my own. I learned one thing, made examples myself, applied them, and studied them further by searching YouTube and Naver for the topic. 2. Introduction by typing the theory directly - I don't understand why you explain the content that you could have prepared in advance with a PPT and lectured on while typing it directly. If you just shortened that time, it would have been a more compact lecture. Even if you thought, 'Students can concentrate better if you type the lecture like this', it would have been better to make the PPT in advance and print it out and add pictures or underlines to explain it. 3. Low sound - This is a bit concerning. I've seen it in other articles too.. The sound is really low. Did you have a problem while filming? If you get a KakaoTalk message in the middle or hear a sound while doing something else, you'll be surprised... Other This may vary from person to person, but I couldn't see it right away because the variables or log messages used in the example were in English. If you just write them in Korean like 'start, end, main, sub, sub1-1, sub1-2, it will be much more readable. Of course, it's a good habit to not use Korean when actually coding, so you can do as the lecture says. I think you can train like this only when practicing, and do the actual code in English like the lecture says.