It's such a shame that this is such an expensive lecture in the 300,000 won range. The overall feeling is that the lecturer just turns on a double monitor, puts the code on one side, and teaches while following along. And he spends a lot of time turning on a CSS file, adding styles one by one to the CSS, and changing the screen to show figma, so if you miss the flow even a little, you can't see what he's doing. And when you look at the final result, the lecturer made a typo and the result didn't show up. 1. Rather than constantly switching back and forth between screens, it would be better to have the code/results on the left and right sides of the screen and keep it fixed. 2. After creating the HTML structure, it would be good to put styles inline right there so that you can intuitively see the results, and once the styles are complete, move all the styles you've put in to the CSS file so that you can see the overall flow, but this doesn't show the HTML code and constantly switches back and forth between the CSS -> Figma screen, putting one line in the CSS file, looking at Figma, putting one line in the CSS, looking at Figma, and so on, so I didn't get it. How should I explain this... To use an analogy, I bought a course called 'Dressing a Fashion Model (HTML) with Clothes (CSS)', but when I open the lid, I often don't see the form of the fashion model (HTML) and only focus on the clothes (CSS) that the person is wearing...? When I come to my senses, the model is already wearing clothes, but the camera only quickly passes by the process of making clothes and occasionally shows the model, so it's hard to see how the model is wearing the clothes. In other words, the process of putting clothes called CSS on top of the existing HTML structure is not visible, but only the process of completing clothes called CSS is visible, so I can't see the flow of whether this person is making pants or arms... I can't explain this in words. I wonder if it would be better to have all three of these on the screen: HTML, CSS, and Figma (or the result window) and mark them as comments above the HTML class that is currently being worked on with CSS... There are just too many screen transitions. In less than 10 seconds, figma -> insert a line in css -> shows html for 1 second, then -> goes back to figma -> goes back to css, inserts a line -> shows the result window again. (Or just keep going back and forth between css -> figma and only moving the css code...) And the instructor goes like this, 'If you put this in, that will appear~ If you put that in, this will appear~', and when you come to your senses, something has been created and the big picture is not well drawn. Considering the price of 300,000 won, it is quite disappointing. If it was 30,000 won, I would have given it 5 stars... If I had to pick something else... The project doesn't run right away after receiving it. Something like having to turn on the backend or some additional process is needed, but when you just turn it on, it turns white and some parts don't come out, which was inconvenient.