Spring DB Part 1 - Core Principles of Data Access

I don't usually write reviews on the internet, but I'm writing this because it helped me a lot. Like other lectures by Knowledge Sharer, this is a good lecture based on thorough preparation as well as the instructor's own development skills. It is really helpful in terms of content, but it is especially recommended because it always considers how to convey the lecture well based on the listener. While showing the source code or official documents at the appropriate time, it only goes as far as necessary at that time, and as always, the stories of usage experiences in the field are also helpful. I was studying DB access technology, and it helped me a lot with the underlying principles and the questions that naturally came up. Thanks to this, I was able to save a lot of time. In particular, the exception handling issue was really helpful. I was quite confused about exceptions while learning JDBC, but 1. You covered the basics of Java exception concepts in a solid manner, 2. You conveyed usage trends in the field and gave clear instructions on how to use them, which was especially helpful. In fact, I started developing on my own and have been studying with Younghan's lectures since I only knew how to do the multiplication table. It's been about 8 months since I started studying with Younghan's lectures, and each lecture has been really helpful. In particular, since the lecture is conducted through the instructor's live coding, I would like to recommend it because you can also acquire knowledge about using IDEs and writing good codes. Thank you always.

I am a job seeker who studied only Java grammar and watched all of Younghan's lectures in the order of JPA -> Spring roadmap. (I think the order changed, but when I started, there was only the Spring basics ㅠㅠ) I think I was able to get here without much difficulty because he explained in an easy way that even I, a beginner in programming, could understand what problems ancient developers felt and how they developed. I think it was because I had listened to the advanced lecture before, so when concepts like templates, callbacks, proxies, and AOP came out, I found them interesting and thought that they were used in this way. Later, when I was creating a function, I thought that I should introduce patterns when I had repetitive code or dependency problems. If I had started with a book like Projects with Spring, I might have been satisfied with just using Spring, so I think it was a good decision to start with Younghan's lecture :) As you said while waiting for DB Part 2, I am trying to move beyond the study stage to the acquisition stage, but I don't know where to start, but I plan to follow Younghan's advice and create small projects step by step. Of course the lecture is good, but I think the direction you give me at the end is a great motivation for me. Thank you so much^^

I highly recommend this to those who have thrown exceptions in their company code or lack the concept of transactions :) Thank you for providing a unique and excellent lecture that raises the average skill level of domestic backend developers!!

Kim Young-han!! Kim Young-han!! Kim Young-han!!

Not only the lecture content, but also the good words in the last video gave me a lot of strength. Recently, I feel like I've been studying after work out of inertia without any particular goals, so I wondered if this was really right? Is this really not my path? Many of the parts that were frustrating have been resolved. Thank you!

"Applying Object-Oriented Ideology to Lectures" Mr. Kim Young-han's lecture is not just a lecture that puts the concept of "DB access technology in Spring Boot" into your head as an implementation. This lecture creates an interface called "DB access technology in applications" in the students' heads. And the students get "JDBC", an implementation that implements that interface in a Java environment. Therefore, students who take this lecture do not need to study from the beginning even if they change the framework to Node-based Nest.js while using Java-based Spring. Since they already have a solid interface in their heads, they only need to put in an implementation for that environment after a short period of learning. I listened to this lecture and understood it. Why do companies say that they don't need engineers who are fascinated by a certain framework and only know how to implement it? In this era where technology changes rapidly every year, I felt that developers who have a good overall interface are more important than having a perfect implementation (of course it's important, lol..). That's probably why big companies value CS knowledge. While listening to this lecture, I, who had only thought of all concepts as implementations in the Java environment, had a big realization. "Why didn't I think of programming in an object-oriented way when I always used an object-oriented language?" I would like to express my deepest gratitude to Kim Young-han, who helped me in my development process. + If you are wondering whether you should take this lecture as well after taking the JPA lecture like me, definitely take it. However, if you have never worked on a project using Spring Boot, I recommend that you first take any topic. As I said earlier, this lecture is a process of putting the abstract concept of interface into your head, so it may be difficult to understand at first. If you listen to it after experiencing it once as a project, you will be able to enjoy the lecture with exclamations of "Ah, so this is how it works~"

I only know how to do CRUD, and when I occasionally encounter DB issues, I feel like my knowledge is fragmented and there is a gap somewhere, but this lecture fills in the gap. It was easy to understand because it first introduced me to the background of the birth of the technology, and when I Googled, I quickly understood what the posting meant, so I was able to dig deeper as if I had wings for development. I guess the basics are important. And I don't think there is anyone who covers the basics as well as Younghan. Younghan, thank you for your always great lectures. Maybe because you make your lectures with sincerity, when I look back at the parts I thought I understood, I see something new. I'm currently preparing for a job, but if I hadn't come across this series, I think it would have been more difficult to get a job. Your lecture skills and knowledge are so rich that I've never encountered them before, but when I listen to your lectures in a series, I can vaguely understand what you're thinking about and what you're trying to teach me, so I respect you in some way. Thank you again for your great lectures, and I'll always support you in the future!

Thank you for always giving great lectures.