･
Reviews 2
･
Average rating 3.5
Over 90% of the class consists of the instructor coding and muttering to themselves. There's hardly any explanation of why the code is being written here, or why certain arguments are needed. They occasionally attempt to explain the gRPC core code, but it seems they haven't prepared or don't know enough, so they gloss over it. You only get about 10 minutes of useful gRPC content in the entire class. About 20% of the total time is wasted debugging parts that have nothing to do with gRPC (e.g., incorrect variable types). In fact, sections 1-3 contain absolutely no gRPC-related content. It's advertised as a server structure that receives praise in real-world applications, but it doesn't seem related to the title. There's no explanation of why that package structure was used, or any discussion of its advantages in terms of maintenance or design patterns. I stopped listening after chapter 6 of section 4 because it wasn't helpful, and I'm writing this review. If there's good content in sections 5, 6, and 7, and I've judged too hastily, I apologize.
Hello, first of all, I'm sorry for not providing you with satisfaction. This lecture was one of the first lectures I started filming, and I think it was a time when I had many shortcomings. So, it seems like there are many awkward parts in the lecture. First of all, the part where I gloss over things is intentional. I was wondering if it would be right to explain this part, but I skipped it because I thought it would be good to find out on your own. The reason for this is that most of my lectures have this concept and method, so I proceed with the topic in a way that you look at the sample code, write it together, learn it, and then study it yourself. Since this is the topic, the lecture is naturally prepared to foster a certain degree of independence rather than spoon-feeding every part, and I have put a lot of effort into having time to work together rather than providing the completed code as it is. So, it seems that some people are not satisfied with this part. Also, in terms of language, Golang basically provides autonomy as a major feature. Therefore, the term "specific design pattern" seems too far from the Go language as a formalized pattern, so these patterns were not covered much. However, since this is also my excuse to represent those who are taking the course, I will try to come back with better lectures and content in the future. Thank you for taking the course!! :)
