This was a lecture where I could experience the design thinking of a "true senior" based on SOLID principles. I initially focused on just watching the lectures because I felt my concentration slipping when trying to follow along with the examples, but the level of immersion from the midpoint onwards was incredible. Before purchasing, I saw the game examples and wondered if it might be a light course, but that was a misjudgment on my part. It was a lecture that allowed me to develop design thinking and perspectives that are hard to experience in practical work. I look forward to the future where I will have grown to the next level after reviewing this. Thank you for the great lecture.

I think it will be a great help to watch this again whenever I need it. Thank you for providing such a great lecture.

This is a great lecture that every developer should watch. I'm leaving with a lot of great insights!

Every time I revisit Young-ho Cho's books, lectures, and seminars, I experience a fascinating sensation of seeing things I hadn't noticed before. I am certain that for anyone who wants to express and explain terms like the SOLID principles, cohesion, coupling, and encapsulation through code and object-oriented programming, this will be a choice you won't regret.

This was a truly satisfying lecture!

After watching the basics, I'm now watching the advanced course and it feels like getting a shot of energy. If you have time, instructor, I think it would be great if you could prepare a course on object-oriented design/implementation in the AI era.

A lecture that changes your perspective on design

The speaking style was a bit stiff like a Korean language teacher, which made me feel drowsy, but the content was really excellent!

This is a must-take course for developers. It's designed for everyone from beginners to experienced professionals, with a structure that solidly builds your foundation. While taking the course, I felt validated and recognized in areas I was already good at, and when topics I wasn't familiar with came up, I could easily understand them. Looking forward to the next course!!!!

Thank you for taking the time to respond even to simple course reviews. After taking the class and thinking about separation of concerns, I had some questions, so I ended up modifying my course review. ^^; Objects are meant to handle the business logic concerns of the domain, but at this point, I don't think objects need to take on logging concerns. Should all objects receive logger objects through injection? Then would logger need to go into every object's constructor... I'm curious if there's another elegant way to handle this. Also, I think contextual information is needed when logging... Should objects internally receive contextual information as well... then would this also need to be injected? It's difficult. I would appreciate your guidance. Have a happy day today as well.