Toby's Spring Boot - Understanding and Principles

Hello. I am a developer with over 7 years of practical experience in Spring. After taking the course, I would like to tell you the conclusion I felt. Just like Toby's Spring book, I hope many developers will take this course. While studying Spring, I came across Toby's Spring and naturally got to know Toby. When I tried to read Toby's Spring book, developers around me said, "Read Toby's Spring later when you have more experience." Of course, I thought there must be a reason why senior developers around me said that, and I ended up reading Toby's book late. In addition to the technical content explained in any book, I received insight on how developers can solve problems they encounter while developing, and after reading the entire book, I was left with regret thinking, "If I had read the book a little earlier, wouldn't I have grown into a better developer?" Toby's Spring Boot covers the technical aspects just like the book, but it also includes the basic principles of the web, which lowers the entry barrier for beginners, and I thought the lecture structure was really delicate. The process of presenting a problem, solving the problem, refactoring, and confirming that there are no problems through test code was very impressive, and when I had questions during the lecture, I thought, "Is he watching me on CCTV?" He answered those questions just like that. The process of gradually removing "my" and converting it to Spring Boot while creating my own Spring Boot was amazing. I thought that the more "my" disappeared, the more Spring Boot became mine. Lastly, when I encountered a problem while developing, I did a little deep dive to check the logic after figuring out how the dependencies between beans were linked to confirm the operation. At this time, to find out the dependency, you check by setting a Break-Point, but instead of that method, you showed us how to check which Bean was uploaded, so I think you showed us a way for other developers to easily deep dive. After reading Toby's Spring, I always wondered when the next book would come out, and it was great to meet Toby through the lecture! The good voice and tone, and the detailed explanation that made it easy to absorb were really the best. I recommend the lecture to beginner developers around me, and I'm really looking forward to the next lecture! Thank you :D

I am a current employee who first encountered Spring with Spring Boot. I had no problem using Spring Boot as a tool. However, I always had an itch about why Spring Boot came out and how it developed. This lecture is a great lecture that scratches those itchy parts very thoroughly. Thank you, Tobi, for scratching the itchy parts so easily. 👍 (The part where MyXXX annotations are changed to Spring Boot annotations was really scary. 🥶)

I know it took a long time for the lecture to come out. Now that you've started the first lecture, I hope you'll continue to give good lectures :)

It was a good time to understand how things that make Spring Boot magically convenient actually work by making them myself, and I think the learning tests that were conducted during the process were really good. Personally, it was good to learn the core principles and concepts of Spring Boot overall, but 1. Create a simple solution and then refactor it in a slightly better way 2. Refactor and check whether the results before and after are the same through tests 3. At first, I checked the results by running it myself, but as it became more complicated and repetitive, I changed it to an automated test This method was more interesting and I learned a lot. I'm looking forward to the next lecture! :)

Thank you for the great lecture. I got used to the convenience that Spring Boot provides, so I neglected the actual operating principles and concepts. Thanks to Tobi, I was able to fill in my shortcomings and it was a good stimulus. Thank you. I will also wait for Spring 6.

I used it without knowing clearly what parts Spring Boot made convenient, but I am happy because the more I listen to the lecture, the more my perspective on Spring Boot seems to broaden. Thank you for making such a good lecture! I look forward to the Spring 6 lecture!

Oh, thank you for the wonderful lecture. Take care of your health, and I believe you will continue to teach the essential and basic contents of Spring Boot in an easy-to-understand manner with better contents in the future. I hope that based on the disclosed lecture contents, it will be an opportunity for me to review the basics again. Thank you

This lecture is not a lecture that teaches you how to write good code, but a lecture that teaches you how to become a better developer. When I first listened to the lecture, I thought it was a lecture that simply explained why Spring Boot is good and how to use it to make good use of it, and the internal structure. However, as I listened to the lecture (especially in Chapter 10), I felt that he was teaching and persuading me about not only simple Spring but also what we can do when we understand the technology we use, and what choices we should make to solve any situation we face. When I understand the internals of the technology I understand, I can reason about the situation, which leads to trust in my code, and at the same time, I can develop at a much faster speed, and at the same time, I know where to look and how to react immediately when a problem occurs. If I dare to infer the intention of Mr. Toby's lecture, I think he wants to make it possible for developers who are afraid of looking into the internal structure to actively understand the internal structure. Even huge projects are just pieces of code in the end. I think he wanted to make it so that we can look inside and see what kind of design well-made projects have, how the code is written, and what choices are possible if we understand the stack we use, so that we can learn and apply them without hesitation. I thank the teacher for creating a great lecture, and I will look forward to the next lecture. :D