Objects - Basics

I took the course after reading the book Object-oriented facts and misconceptions. Personally, this course helped me the most. When I read the book, I had vague ideas about the distinction between messages and methods, responsibilities, cooperation, and roles. This course, although not perfect, helped me resolve some of them. In particular, the best part was that it taught me how to apply object-oriented to the Controller > Service > Repository MVC structure that we generally use. I will review the course content again and organize my thoughts. Since you said it is a basic course, can I look forward to the next one? Thank you for creating a great course.

As I became more advanced in terms of simple implementation, I looked for Cho Young-ho's books a lot, but sadly, I couldn't approach <Object> in terms of quantity and difficulty. But now I'm so happy that I can approach it as a lecture. The basics feel like learning <Facts and Misconceptions of Object-Orientedness> in more detail. I can personally realize the necessity of it by looking at cases of transitioning from procedure-oriented to object-oriented. I've only seen the beginning, but it's been a great help in recalling the content that I had forgotten for a while. However, there's something really disappointing. Since you read the script, you convey the content in a stiff literary style. As someone who knows the instructor's smooth and immersive teaching skills, I really, really regret this part. More people should know the instructor's charm..!!!!! He speaks with ease in every word, and he explains difficult concepts in an easy and fun way😭 I remember you saying in another lecture that online is more awkward than offline, so how about creating an environment like an offline lecture for the next lecture? I am cautious about making this suggestion, but I would like to tell you that it comes from my heart as a fan. I have two fathers. One is my biological father, and the other is Professor Cho Young-ho🤭 He is someone I am very grateful to for broadening my horizons. Thank you for always giving me great lectures!🙂

Online Classes often have lower information density than books due to the nature of their content, but this lecture should be considered an exception. The cohesion of the code explained in the lecture is directly applied to the lecture itself, making it a truly high-cohesion lecture. In your previous work "Object," you explained the massive concept of design with incredible precision, and throughout reading it, I could feel the instructor's bone-cutting effort to write the book. In the lecture version, seeing you explain tremendous content more concisely than the book to the extent that I wondered if it was possible to contain this much in an online lecture, it was such high-quality content that I worried whether you had any more bones left to cut. Watching every single sentence of the script written with high cohesion, I indirectly experienced skills that went beyond what you showed in the example code. Although it's a relatively short 5-hour lecture compared to others, learners will need to invest at least three times more time to truly absorb the essence of this lecture. Because of this, some people might find the lecture somewhat difficult to follow, so I'd like to leave a small tip. One monitor isn't enough. I recommend watching the lecture in at least a dual monitor environment with the video on one side and the lecture materials on the other. If you only refer to the lecture materials in the video, the screen might move on before you fully understand, and there are contexts that can only be understood by comparing materials before and after. Also, the movie domain is an essential element for conveying the overall content of the lecture. You might feel tempted to quickly skim through it, but I recommend repeatedly reviewing the materials and thinking of it as a service you originally developed, keeping it in your mind. This way, you can focus more on the essence of the lecture. Since the core is about how to manage code changes, you need to follow along with what changes occurred in the domain used as an example in the lecture to receive the deep message about how to write code that's resilient to change. For those who find object-oriented programming somewhat abstract, I have no doubt that if you thoroughly understand this lecture, you'll experience a paradigm shift in how to write and view code.

One of the best lectures I've taken this year and it completely changed my perspective on development.

In a lecture that deals with IT technology, a lecture that deals with the subject of development paradigms seems to be of great help to the learners in building their knowledge. Other Spring or Java lectures are good, but I think this kind of lecture that makes you think at least once before typing is really good.

This is a great lecture. I think it will be helpful to all developers, regardless of their experience level.

It's the best..

If you're a developer who uses object-oriented languages, I highly recommend this lecture. Just as I bought and was reading both books, "객체지향의 사실과 오해" and "오브젝트", I discovered this lecture on Inflearn! What exactly is object-oriented code...? I was always a new developer pondering this. What others say: high cohesion, low coupling. Closed for modification, but open for extension. What kind of code is that really? How should it be written? I was always curious, but thanks to Youngho-nim, I'm slowly but surely gaining understanding. What I really liked was that he not only explained but also illustrated the structure with examples and implemented it with code. He is truly a person I'm grateful to for changing my perspective on development, design, and good code. I will study even harder in the future 😄 Please continue to provide many good lectures in the future 😊😊