I only did backend, but there were so many parts that I was stuck on when designing the front end, so I bought it and listened to it. When I first watched the lecture, I was working on the design in a state of vague understanding, but then I suddenly thought, "I heard something in the lecture, but I don't know exactly what I'm using?" Every time I went back and listened to it again, I was able to understand and use it clearly again, unlike when I first listened to it. If there was more in-depth content, I would pay to listen to it. (23-02-23) When something doesn't work while developing, I find the problem and put in the command I want, and it's so fun to see it change exactly. / This may be TMI, but when I first listened to the lecture, I thought the speed was too fast, and I thought I would understand it but not learn anything while watching the instructions on the homepage, but it really shows its value when I read it twice. I recommend that others read it once and try designing, and when you read it twice, don't read it thoroughly, but go to the category of parts that don't work and look at them again. It's really... not a real country, but a real country. // When I have some time, I should take a look at GitHub and JavaScript courses.