Java/Spring Junior Developer's Mistake Notes

This is a lecture that is like a stepping stone for development skills. Veterans create different results with deeper knowledge and a broader perspective even when doing the same work. I think this is the scary thing about years of experience. This lecture imparts knowledge and techniques that can be accumulated through many years of experience. The instructor kindly introduces valuable information and techniques accumulated through his persistent obsession with development and various experiences to beginners like me. When I first saw it, I was surprised the whole time. I was now able to explain the concepts that felt vague in words, and I immediately studied object-oriented programming and applied it as instructed, and refactored it, and the structure of the project became cleaner. When I first saw the lecture, I was still inexperienced, so I was not able to apply the contents you mentioned in various ways. After that, I thought of this lecture while working on a new project. When I watched the lecture again and applied the contents you mentioned, I felt that the code was incomparably improved compared to before, and my project mentor and team members all praised it for being easy to read and well-written. I think this lecture is a lecture that broadens your perspective. It goes beyond simply correcting mistakes and learning the know-how and knowledge of experts, and I think it is a grateful lecture that shows various choices that beginners cannot see when making a choice.

BAD The sample code is too similar to my code 🫣 I'm somehow building a server on my own in an environment without a shooter, but I'm a bit lost when I want to go to the next step 😮‍💨 I was lost, but after listening to the lecture, I think I'm starting to get the hang of it. Thank you so much 👍🏻 I wish you'd upload more lectures related to design 🙏🏻

This was a very helpful lecture for me. I was so happy that you taught me at least what not to do while I was just starting to think about good design. Also, since you provided sources for all quotes, I think it was a better lecture because I learned a lot of good books. Aside from the lecture content, the tone and lecture progress were neat, so I enjoyed listening to the latter half where you explained many terms. Thank you so much for making such a great lecture!

I listened carefully. It was good to hear about the parts that I was worried about at the boundary between theory and practice from various perspectives. In particular, as a junior developer, I have to study, but I think it would be good to listen to keywords that are good to throw out when I don't know what to study, so I think it would be good to look at it again once in a while to recall the concepts.

I am a 6th year developer. I listened to it out of curiosity, and even I saw that there were a lot of really useful tips and parts that I had missed. Thank you.

It's the best!! If other existing lectures taught you how to fish, this lecture gives you hints on how to fish better and how much better, so you can find a better way yourself??? As the years go by, you invest a lot of time in designing, and when you create a system, you think really, really hard and search for a better way, but you're not sure if you're doing it right, and there are many times when you can't find a better way. This lecture was really helpful at that time. This lecture won't be for beginners. As the title suggests, junior level 2, 3, 4 year olds, if you listen to this lecture, you'll really feel something sparkling. I was half-hearted because the price was not cheap compared to the lecture time, but I paid right away after seeing the first question at orientation. There's nothing to throw away from the beginning to the end. There were some difficult parts in the middle, and there were many parts that I already knew, but they're all like gems. Thank you for making such a great lecture. Please make even better lectures next time^^ Happy New Year~

I was thinking about what game to play after using up my half-day vacation, and then I started watching an Inflearn lecture that I had previously purchased but hadn't watched while eating lunch. I started with the feeling that I should just watch it at 1.5x speed since it was short, but I lowered the speed right away and started taking notes, and it seemed to take more than twice as long as the lecture. I liked the lecture so much that I ended up watching it all the way through without taking a break. In the end, my half-day vacation was gone, but I still don't feel bad about it. Personally, I think Section 2 OOP was the hardest. Still, it was nice to listen to. Actually, I was just looking at Section 1 roughly, but I think I started watching it from Section 2. I also liked the overall explanation of the test part. In my case, I didn't really understand the integrated test, but it helped me with that part, and I also got a reference that I don't have to test private (good). The explanation is clear overall, and it seems to have been appropriately divided so that it wasn't too excessive (there's no part where you have to fully map all data between all layers). The last section is written as reinforcement, so it seems like you added it in the middle, but the explanation on the hexagonal side was the goat. I had seen the book introduced in the lecture before, and I had seen other videos and books, but I think this is the easiest and best explanation I have ever seen. I think you explained it well with a vacuum cleaner, and I especially liked the part where the explanation on the improvement of the existing layer was connected to the hexagonal. When you explained the layer in reinforcement, you said that you didn't need the service side DI before, but this time you added it subtly, so I thought, "Oh, you're trying to connect it with the hexagonal," but it was right and it was fun. In Toby's Spring Boot lecture, it was really good that all the bait that was dropped from the beginning was recovered at the end, and in this lecture, the layered improvement that was explained from Section 2 was combined into the hexagonal in the last lecture, which felt similar and good. If you are a complete beginner, it might be difficult to understand unless you have studied a little. You need to have some experience with Spring to understand it. Even then, 'Huh? Where have you heard of it?' It seems great even if you only take it. Also, if you have done some work, it seems like a really good lecture. Of course, each concept is not explained in detail, but it is explained quite clearly and it is not too radical, so it was a good lecture. I don't know if I liked the lecture already and everything seemed good, but I felt like the atmosphere was lively because the PPT style changed for each section.

A great lecture that made me realize that I was not a developer but just a regular person who codes.