Spring Core Principles - Advanced

This time it was really long. I was so happy that I could finally understand AOP, one of the three major technologies of Spring. It was like an impregnable technology to me, like pointers in the C language. I really liked how you explained it step by step this time. I don't think there is a lecture or book that teaches AOP this easily. If you want to learn about Spring in earnest, you should definitely read it. And as a thank you to Yeonghan, I'm going to write about my Spring developer challenge. ============== When you try something new, you really need a lot of energy at first. ...(omitted)... First of all, it's really important to make a study habit. And when it comes to studying development, you have to try everything and code. You can never make it yours by just reading books and listening to lectures. I recommend that you study consistently for 3-4 hours on weekdays and 8 hours on weekends. =============== October 2020. I have been a Python developer so far, and I acknowledged that my career was at its limit and wanted to change my career to the Spring backend, so I sent an email to Younghan asking for advice. At that time, I received the above response from Younghan. It was a bit shocking, and I felt that I needed a lot of determination. In terms of years of experience, I was already at the senior level, and since I only knew a little about Java, the challenge was really difficult. I failed the interview repeatedly. I remember that when I failed the interview with Woowa Brothers early last year, I didn't study well for almost a month and a half. As Younghan said, 3-4 hours was realistically difficult, but I tried to do at least half of that. In fact, the content of this lecture was not mentioned often during the interview, but thanks to the content of the lecture that Younghan covered, I was able to develop an eye for looking at backend technology more deeply, which was the most helpful. And the fact that I had to study at a much higher standard. (I think I tried to make the derived content from the lecture my own.) My efforts worked... I went to one of the Nekaraku Cups at the end of March this year. I still feel inadequate, but I am excited and a little worried because the long 1.5 year preparation period has ended and the opportunity has been given. When COVID is over and I get used to my new position, I will go and thank you in person. Thank you, Younghan.

Spring AOP Education Masterpiece. The best lecture I'm sorry to the instructor that the maximum number of stars I can give is only 5. Thank you so much for the great lecture. As a side note, if you practice following the instructor's code and then debug the internal implementation logic of SpringObjenesis, CGLIB, and JDK dynamic proxy (ProxyFactory, ObjenesisCglibAopProxy, etc.) separately, you will probably get much more out of it. Personally, I debugged the moment of initialization with ProxyFactory proxyFactory = ProxyFactory(Component without interface); and went through various procedures according to the rules until I saw with my own eyes that it uses objenesis when creating and returning a proxy object as the result value of getProxy(). If I hadn't watched the lecture, I would not have understood anything because I didn't know the outline of the workflow at all. Also, I felt that my understanding of Spring AOP greatly improved while separately looking into the process in which the AspectJAutoProxyRegistrar class related to EnableAspectJAutoProxy gets types annotated with @Aspect and uses BeanPostProcessor in the subsequent logic to register proxy objects as Spring beans instead of actual objects. I am deeply grateful that you showed me the big picture first so that I could understand the detailed operation of the actual logic.

It seems like Younghan's lecture is not about opening a door, but about holding the doorknob and turning it. Thank you for always showing such great lectures.

After reading Toby's Spring Chapter 6, I had a mental breakdown and put the book down for a while, but I'll have to finish this lecture and go back to reading it. (Review after completing the lecture) At first, I was overwhelmed by the size of the lecture, which was 125 lectures, but as I listened to it, I understood why the lecture size was so large. As you said at the end of the lecture, I'll try to get through more code and look at more references. Now, I'll have to go study other design patterns that I don't understand enough. I'll come back next time with a better look.^^

This was the first time since Supporters that I contributed to the lecture (manual) even a little bit, so it was a more meaningful advanced lecture than the previous lectures. I hope you will continue to give good lectures :)

I dreamed of becoming an embedded developer during my undergraduate years, and luckily I got a job at a power electronics-based manufacturing company. I thought I would do embedded development at the company, but I was assigned to the SW team and was put in charge of SI work. (I said I wanted to do embedded development during the interview...😿) So I started wandering around doing development that had nothing to do with my major. As time went by, I was assigned to a web socket-based communication application development project, and I heard that Spring was a good way to start web development, so I started developing using Spring for the first time in my life. But Spring wasn't easy... (I really didn't understand it when I first encountered it. In particular, the part where you write code using annotations was unfamiliar to a novice developer like me. Oh, and I didn't have a mentor, so I developed it alone.ㅠㅠ When I asked the team leader for technical advice, he didn't know much. And he was more interested in sales than development.) I thought I couldn't go on like this, so I bought Hyangro's book and studied it, but even that book was difficult for me, who had no foundation in development. ㅠㅠ While I was wandering around like that, I found Infraon and got to know Younghan there.... (I'd like to say that getting to know Younghan was a turning point in my development life.) After listening to Younghan's Spring introductory lecture, I felt a ray of light in my frustrating development life. 😍 And then, as if possessed(?), I bought and listened to the lectures I needed. Thanks to Younghan, I was able to successfully complete the web socket project. After that, I took Younghan's JPA lecture and refactored the existing legacy using JPA, and naturally became interested in web development, and I made up my mind to become a web backend developer....! (At that time, I think I always listened to the lectures for 2-3 hours after work on weekdays.) After I decided on my career path, I felt that I needed specialized knowledge, and I thought it would be good to receive professional education, so I went to graduate school. ㅎㅎㅎ And as time passed, the company started to accept projects that were far from web development again. So I decided to quit my job to change my career to a web developer, and I quit my job while preparing for a job change. Yeonghan is my first developer life teacher and role model. Thank you for always making great lectures. And I love you.❤️

After completing the course, I think the instructor must have worked very hard to create this course. I think it would be hard to find a course that explains complicated concepts like proxy and AOP step by step with examples in an easy-to-understand manner. Overall, I feel that the buildup of the course is really detailed and well-organized. In my case, while learning about template callbacks, I had doubts about whether these concepts were connected to AOP, which I had briefly learned in the early Spring course. However, after passing the proxy part to some extent, I was convinced that all the previous concepts were the foundation for AOP. I think it was a course that conveyed the instructor's hard work for us. Thank you for creating a great course :)

You teach advanced techniques so easily. Thanks to you, I had fun completing the course. ^^