･
Review 1
･
Average rating 5.0
It is definitely a really good lecture. I am listening to everything from Spring Batch > Security > OAuth2. Since everyone else has mentioned the advantages, I would like to tell you about my suggestions(?) or regrets. I thought it would be helpful to check all the source code levels of Spring in debugging mode. Of course, the instructor checks by setting breakpoints in advance, but it doesn't seem easy to follow the screen that passes by quickly. Of course, if you say that you have to know everything to use a certain technology!!, I have nothing to say, but I think the lecture would be more compact and cost-effective if the instructor explains the theory part and ends by quoting some source code. It is definitely a good lecture, but it takes a lot of time to learn everything, including the debugging process, and if you take this lecture to use it in practice right away, you might think that you should postpone applying it to practice. I am leaving a review in the hope that the instructor will continue to make better lectures in the future.
Yes, thank you for your sincere evaluation^^ As you said, showing the source level processing process using debugging in the lecture may not be a necessary element in some sense. The lecture time is relatively longer, and there are also things that are not easy to understand even after seeing the debugging process once. Nevertheless, the reason for including debugging elements in the lecture is to help you clearly understand the internal processing of the framework or library. Of course, you do not need to know the internal processes and flow of all modules and APIs, and you cannot know them. From my perspective, if it is determined that knowing the internal processing process is important when implementing a function, I explain the overall processing process through debugging. Debugging does not mean that it ends with debugging itself. The purpose is to develop the ability to extend or apply the API as I want, beyond simply using it, by clearly understanding the purpose and principles of the design of the API through debugging. Although we did not design or create Spring Security directly, it is a good way to indirectly participate in the design of the core technology through debugging and partially experience the principles of implementation. If this process is repeated and accumulated, not only the basic use of the API but also a deep understanding of the technology will be possible, and complex custom applications will be possible, and you will be able to respond quickly when exceptions or issues occur. However, if you look too closely at the source level, you will miss the whole picture. Because it can be done, you should take the method of analyzing and adjusting it according to your level and understanding ability. I will continue to think about how to incorporate debugging utilization at an appropriate level into the lecture through speed adjustment and develop it. Thank you again for your valuable evaluation^^
