GraphQL 완전정복 (키오스크를 만들며 배우는 풀스택 과정) - [2024 부분 리뉴얼]

Overall, the lecture time is short, so there is no burden, and the answer to questions is fast. The disadvantage is... They explain by showing the already written code in PPT format (If you click, the existing code flies away and the code is added smoothly) Even without that, since I listen to the explanation while looking at the unfamiliar code structure in PPT format, it is hard to understand the flow of the code and follow along. You may think, "Since there is a lecture code on GitHub for this part, why don't you just copy and paste it?" But if you intended to do that, you should have saved the code by branching GitHub by lecture section part.. The GitHub lecture code was already completed code, and it was very tiring to compare these codes with the lecture I am currently listening to and copy and paste them.. I listened to the server part lecture at the beginning of the lecture and ran passionately for four hours without stopping, but when I entered the front part, I thought that the tuition fee was too expensive compared to the lecture quality, but I thought it was because I got really good answers when I asked questions, so I let it go. Lastly, since it is not a seminar like a technology tech, I think there will be more people who dislike this kind of PPT-style lecture than who like it. Furthermore, the code is not that complicated or long, so I think it would have been better if you had added explanations while typing the code together. Following the lecture with PPT, it really ㅠㅠ is so tiring for the listener. I just clicked the “I watched” button for the latter half of the lecture and skipped over it..

I completed the course. I took the course because I wanted to create a full-stack service after learning the basics of Javascript, HTML, and CSS. There are also React and Vue, but Svelte is easy and hot, so I chose this library. This course covered the entire process of creating a smart menu service from scratch. The explanation was also very detailed, so I understood it well. /// What was disappointing was that I kept getting stuck during the course. I made typos when I wrote the code, but there were many important typos in the lecture videos, so I had problems when I just watched the lecture videos and followed along. There were also occasional typos in the example code, so whenever I ran the server and tested it, I was often confused as to whether I made a mistake or there was a typo in the lecture content. (I don't understand how other people who wrote course reviews could proceed with the course without asking questions on the bulletin board.. Didn't they complete the course?) The environment in which the course was conducted was MacOS, and I was in a Windows environment, so the server execution command was not meteor but meteor.bat, which was different from the course. Or, there were problems such as the course proceeding differently because the course and the current meteor version were different. Still, when I asked questions about these problems on the community bulletin board, the teacher answered them well within a day or two, so I was able to continue the course. // From Section 4, which creates a SMART MENU, it was okay at first, but as the code got bigger and bigger, it was very important to compare the differences with the previous code when a bug occurred, so I felt the need for version control, studied git separately, and applied it while listening. As I listened to the class while creating a branch every time the code of each section ended without a bug, and committing every time a small chapter in the section ended, I was able to quickly deal with bugs that occurred after Sections 12 and 13. I recommend that beginners like me study git separately and use it in class. Also, in class, regarding debugging, if there were more parts where you check the terminal window for the backend and the console window for the frontend, wouldn't it have been better for beginners like me? Since this is basic content, it doesn't seem to be included in the flow of the class. However, I thought it would be good if you made a brief mention of git or debugging methods in class. // < Subtitle Coverage Issue > There were videos with subtitles in the middle of the lecture, but when you renew the subtitles, please make sure they are positioned above the play bar. The subtitles are covered every time you stop and watch. ㅠ // While I was teaching, I diligently reported the parts that I was stuck on and minor typos, etc., and since the teacher said that he will be renewing the course in March 2023 to reflect these parts, I think those who take the class after that will be able to take the class more comfortably. // After completing the class, - I was able to learn about the overall operation of GraphQL and how to operate it on the Apollo server. - How to build a front-end that connects to the back-end easily and quickly using Svelte. I listened hard and understood, but I think I need to do the class two or three times to become more familiar with the structure and operation. Personally, I think I need to study more about creating a front-end using Svelte, so I think I need to do some additional learning. I'm a beginner who only watched videos of react and vue, so I don't know much, but when I made a service using svelte, I felt that svelte was easy and intuitive. There's a svelte-only integrated framework called svelteKit, so I wish the teacher would make a lecture on this part too. ㅎㅎ.. The lecture content is really informative, so if you want to listen, please listen.

The composition is so good

Thank you for the great lecture. I got used to developing frontend/backed based on graphql, and the cache, link, file upload, and authentication parts were also very helpful. It's my first time with meteor, but I found it useful after following along until the final deployment. I look forward to good content in the future.