토비의 스프링 6 - 이해와 원리

It is plain. There is absolutely no online lecture tone full of modifiers and empty words to extend the lecture time. It is plain and thick, compressed, filled, and organized through several rehearsals. It is clearly different in intensity from other lectures that jump around to see quickly. I think most students will feel the most when they watch the lecture that there are no gaps in the lecture flow. The explanation of Spring did not start until the end. However, after listening to it all, I learned the core of how Spring works through the beginner's guide to the development ecosystem. The target audience includes everyone from beginners to intermediate and above. There are cries of "Beginner!!" and exclamations of "This kind of content??". Starting with a very simple example, it explains classes and objects, and shows the journey to find a more convenient and sophisticated method through relationships. At some point, the concerns that started in order to respond to change lead to design patterns. I shed tears over the past time when I opened the design pattern book and memorized many patterns in front of me. Rather, I can think about which patterns to use for changes. By the time we reach the entrance of the design pattern... Spring proves that it is a framework that easily supports DI by organizing the dependency inversion principle. Just like... students memorize K Ca Na Mg Al Zn Fe Ni Sn Pb H Cu Hg Ag Pt Au or memorize Taejeong Taese Mundan Se Yeseong Yeon Jung In Myeong Seong Gwang In Hyo Hyeon Sook Gyeong Gyeong Jeong Sun Heon Cheol Go Sun Eun (Joseon King's posthumous name), they memorize SOLID with a development book. Likewise, since I memorized it as if I was memorizing it for a test, there was no reason not to understand the content that I didn't understand as the code change process that directly creates the necessary function. Let's exclaim in admiration. As a developer, you need to conduct tests to quickly draw your own code and increase reliability, but this lecture shows you the reason and method of testing for 2 hours, and when you are tired of watching lectures that are full of content that can only be found in manuals under the title of TDD, this lecture shows you just what you need. Rather than talking about the meaning of test code and what is the real test code, the test part is concluded with the line that how to execute the test and how to verify what is more important. The necessity of code reuse cannot be overstated, but it shows which code should be reused and how to distinguish the parts that need to be changed, and the process of creating this as a template. At this time, you can naturally see the concept of callback with your eyes, and it shows how all of this process is completed in Spring. I was curious because it was not a lecture for beginners, but it explained exceptions, and it added a request to the request, explaining the precautions for exception handling, and at the end, it shows the concept and entity of abstraction, and various abstracted functions in Spring. And it concludes that these are actually the sum of the technologies that encompass the concepts learned so far. It was a lecture that showed the intention to put almost everything a developer needs to know into the title of the Spring lecture, approaching it through the beginner's course, and even if functions are added, it eventually covers objects and relationships, patterns and templates, and securing reliability based on tests, and even abstraction to escape dependencies. This is a great lecture that you should carry around with you and recommend to your loved ones as a gift. Let's do some Infraon work~~ There should be a function that allows you to send gifts if you know the email address of the other person's Infraon account!!!! I would like to thank Tobi, who refused to pay a high price for a lecture that only a few people can attend and created a book of martial arts secrets for all developers at Infraon for over 2 years, and I will end this review.. . Everyone!! Run here!!! # I could have been 1st... Everyone who left a review without taking the class 100% is cheating.. Bad!! # Even if you watch just one lecture clip from the domain section, the perfect build-up is enough to cover the entire cost of this lecture. You will regret not watching the other lecture clips. Hwa-ryong-jeom-jeong

It's the advance team. I have Toby's Spring book at my office and at home. It's been 14 years since the book came out, but it's still a great help in understanding the working principles of Spring and the abstractions it provides. I started watching it as soon as the lecture was released, but I was so obsessed that I kept clicking on the next lecture button and it was time to go to bed. There's a process of presenting problems in a situation where functional requirements are satisfied through example code, and transforming it into changeable code by applying design patterns and design principles. It was easy to understand and I was able to take the class with great immersion. I recommend that you look up the keywords that are thrown out here and there instead of just skipping them. Although Spring has been developing for over 20 years, I can feel the greatness of object-oriented design in that its underlying technology is still solid. In the book and in this lecture, Toby seems to be teaching us how to catch fish. I love Toby.

First of all, the video lectures were so engaging that I, who has ADHD, watched 30% of them in one day. Even concepts that seem somewhat abstract to junior developers, such as SOLID principles and object-oriented, were explained in an easy-to-understand manner with examples, which reminded me of a mother bird. In this lecture, I felt that the maestros who definitely knew the truth had concise and simple sentences. It felt like eating a well-prepared Korean meal. I felt the same way when I listened to Object's Cho Young-ho's offline lecture, but Toby's lectures were so natural and logical that I felt like he had prepared a script. Of course, I don't think there is a royal road to learning development. However, with this level of compass, I don't think I'll get lost. Also, the way he explains complex concepts in an easy-to-understand manner was a great help in my studies. Through this lecture, I was able to approach difficult concepts with confidence. And as a side note, this is something I didn't expect because I only read books, but Toby's voice had the power to increase concentration and immerse me. I really liked his calm yet powerful voice.

I haven't listened to the whole thing yet, but from what I've heard so far, I think he explains it better than the first-time college entrance exam instructor, so I'm leaving a review in a hurry. I think he would have been a first-time college entrance exam instructor if Spring had been a college entrance exam subject, because he explains things that were only explained in writing, so that anyone can understand the principles of operation. I think he's accurately DI (instilling understanding without trying to understand) in my head to that extent. After watching this lecture, I'm going to read Spring 3.1 carefully. I've been putting it off because I hate stiff writing, but I think I want to study properly this time. ㅎㅎ I'm always grateful. If I can edit my review, I'll read it all and add a review. I hope you stay healthy and create more great lectures.

Thank you for helping me become a better developer. I am still reading the hardcover edition of 'Toby's Spring 3.0'. When I first read it, I skipped over chapters 1 to 8 and only looked at the practical parts. However, as time passed, I ended up looking at the first part, chapters 1 to 8, again. The lecture focused on the first part, and explained the principles while excluding the difficult parts of Spring implementation as much as possible. Toby's unique build-up method of explaining the principles was still effective. Here are some things I didn't feel through the book, but I felt through the lecture: - The need to separate codes according to the reason and timing of change - A good habit of Opening and Closing at the same time when writing code that requires resource release - How to use IntelliSense with camel case in IntelliJ IDEA - How to use the TimeUnit class to conveniently use Thread.sleep - How to reduce dependencies by separating packages based on DIP (Dependency Inversion Principle) - How to control the environment using Clock.fixed - Double bracket technique that can be conveniently used when configuring Spring Configuration In fact, the things I learned listed above are additional parts, and while watching the lecture, I kept thinking about 'how to create a structure that is easy to maintain'. These parts were not completely resolved even after watching the lecture, but since it gave me some direction, I will think harder in the future. Thank you. Lastly, I felt that the condition was different for each lecture. Stay healthy. Once again, thank you for helping me become a better developer.