I've tried many languages, but I've never been able to move beyond functions. This is the first grammar lecture I've studied all the way through. The reason I was able to finish it was because I had a mentor who helped me get out of studying alone, and my group members who created a study atmosphere together (this part can vary depending on the efforts of the group and myself) and the easy, "friendly", and detailed explanations of concepts. (The reason I emphasized friendliness is because I think this lecture was created from the learner's perspective) This lecture is not for the first time, but for those who have tried coding more than once. This lecture can be taken by both experienced and beginners, but I'll leave a few words for the latter. (Many people in the field take it, so they'll know how to do it well ㅠㅠ) This is just my opinion, so please use it as a reference :) I don't even know how to code, but the lecture volume is 80-100 hours. It's even a grammar lecture. The course period is also set. First, set a goal. The lectures are designed to be completed within 2 months, and that is the best way to do so. (You can listen to them faster, but you don't have to force yourself to go back if you don't understand the previous lectures at all.) Because once you start to fall behind, you can keep falling behind. When the pace slows down, excuses pop up and other things catch your eye. Since the recorded lectures are the base, you can take other classes and do other things at the same time, but I think it's best to focus only on this until you finish it once. (Of course, there's no right answer, lol) If you finished it, you really worked hard. It gets easier from here. The concepts are explained really easily, so you should understand most of the grammar. You can also draw the big picture. (It's okay if you don't. The terms, concepts, and everything will start to feel familiar.) Coding requires a process of making it your own through practice, but even if you think you understand everything while listening to the lecture, if you can't explain it by yourself or code it yourself, you don't know. This lecture is a lecture that is spoon-fed to you. But you have to know how to digest it. Re-listen to the parts that are not mine and make them mine, or start the second full-fledged run (The speed really gets faster from the second time. You can hear it well even at 2x speed!) By making an app yourself (even a simple program is ok), you can really get a feel for where specific grammar is used and why it is necessary. (It becomes fun to learn why it is necessary and how thankful(?) it is.) For example, if you have learned an extension, try solving a problem using it. Problem solving sounds grand, but it is not. When you use an extension while making a program, you don't have to write code repeatedly, so the inconvenience is gone, or you didn't feel any inconvenience, but after using it, you felt convenience.. You solved the problem. (Of course, another problem will arise.. It's okay. Growing pains of becoming a developer..) Keep repeating. Concept & Practice App making is included in the lecture (when I listened, only the app using the concepts before the class was uploaded) I only followed once and moved on (ㅠㅠ) But even after the class, I recommend following the app making several times and repeating it. It can blow away the boredom that can come from just listening to the grammar, and it can also review the concepts you learned before. It is not a simple follow-up lecture, but it explains it one by one from the perspective of a beginner who is trying it for the first time. From the instructor's perspective, please explain all the parts that you may have already become familiar with and just skipped. (Most other lectures just skip over them. It may not be a critical part, but it is a great help to those who do not know anything.) It may be awkward at first and take time, but after 2, 3, 4... it will get faster and you will be able to understand it better. As written in the lecture introduction, you are free to do whatever you want after completing the course. That is because you will be at that level. (However, there will be a new hardship..) I wrote a few words, but it keeps getting longer. Lastly, I want to brag about this lecture. The lecturer answers questions really well. I didn't ask many questions. (Sigh..) It's so obvious, but you can gain as much as you do, so please tease the lecturer a lot.. (It's okay to whine about not studying(?) Ask a lot of questions!!) From a learner's perspective, it's really important to ask questions "well" and "a lot". Don't worry, he'll take them all :) It's important to struggle in development, but if you have someone who can solve it, it's better to ask questions and do something else instead of just sitting there all day because you can't find it even when you Google it. I think the writing is getting lighter and lighter. I wanted to praise the lecture a lot, but it seems like I've only talked about other things ^^;; I haven't talked about the principles and concepts explained with pictures, which are the identity of this class yet ㅠㅠ Alan, thank you so much. My small goal is to go up to Seoul next time and buy you a meal. Until then, stay healthy.. I'll ask you to continue the next lecture. hehe